| To: | Shirshendu Chakrabarti <shirshendu@xxxxxxx> |
|---|---|
| Subject: | Re: [pcp] Process analysis |
| From: | "Frank Ch. Eigler" <fche@xxxxxxxxxx> |
| Date: | Fri, 14 Nov 2014 10:27:16 -0500 |
| Cc: | Nicolas Michel <be.nicolas.michel@xxxxxxxxx>, yves.weber@xxxxxx, pcp@xxxxxxxxxxx |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <CALg+gg=UpskZYxGyiCavtzD5tn5TC3KwNu9UQF=7z+MLJMCarw@xxxxxxxxxxxxxx> |
| References: | <CAO5znat7ceWKn8wf0RKC=GNzagqv3dsa=r-zfFTL4MxgLeue9w@xxxxxxxxxxxxxx> <y0mvbmjdoep.fsf@xxxxxxxx> <CALg+gg=UpskZYxGyiCavtzD5tn5TC3KwNu9UQF=7z+MLJMCarw@xxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.4.2.2i |
Hi - On Fri, Nov 14, 2014 at 12:00:24PM +0530, Shirshendu Chakrabarti wrote: > This can be a probable solution. You can use systemtap to trace the > desired process. [...] Please see, AFAIK, there is no known > integration with PCP for above solutions. systemtap et al. are certainly possible sources of additional data for PCP. We're in the process of building out a richer systemtap-pcp interface. Do you have any more specific ideas about what new per-process or intra-kernel statistics you need collected? - FChE |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: oss.sgi.com - maintenance downtime Friday 11/14/2014 at 10:00 CST USA, Troy McCorkell |
|---|---|
| Next by Date: | test - please ignore, Troy McCorkell |
| Previous by Thread: | Re: [pcp] Process analysis, Shirshendu Chakrabarti |
| Next by Thread: | Re: [pcp] Process analysis, Nicolas Michel |
| Indexes: | [Date] [Thread] [Top] [All Lists] |