On Thu, 3 Jan 2019 23:02:07 -0500
Steven Rostedt wrote:
> On Thu, 27 Apr 2017 23:03:24 +0530
> Pratyush Anand wrote:
>
> Hi Pratyush,
>
> I was digging through old email, and came across this. Our thread sorta
> just died. Are you still interested in implementing "trace-cmd top"?
>
> We've
On Thu, 27 Apr 2017 23:03:24 +0530
Pratyush Anand wrote:
Hi Pratyush,
I was digging through old email, and came across this. Our thread sorta
just died. Are you still interested in implementing "trace-cmd top"?
We've changed the code structure quite a bit since this came out so it
would
On Thu, 27 Apr 2017 23:03:24 +0530
Pratyush Anand wrote:
> On Thursday 27 April 2017 10:19 PM, Steven Rostedt wrote:
> > On Thu, 27 Apr 2017 19:32:43 +0530
> > Pratyush Anand wrote:
> >
> >> I will implement your review comments and will send next
On Thu, 27 Apr 2017 23:03:24 +0530
Pratyush Anand wrote:
> On Thursday 27 April 2017 10:19 PM, Steven Rostedt wrote:
> > On Thu, 27 Apr 2017 19:32:43 +0530
> > Pratyush Anand wrote:
> >
> >> I will implement your review comments and will send next revision.
> >> However, I had couple of
On Thursday 27 April 2017 10:19 PM, Steven Rostedt wrote:
On Thu, 27 Apr 2017 19:32:43 +0530
Pratyush Anand wrote:
I will implement your review comments and will send next revision.
However, I had couple of observation which I was unable to justify:
# ./trace-cmd top -s
On Thursday 27 April 2017 10:19 PM, Steven Rostedt wrote:
On Thu, 27 Apr 2017 19:32:43 +0530
Pratyush Anand wrote:
I will implement your review comments and will send next revision.
However, I had couple of observation which I was unable to justify:
# ./trace-cmd top -s /tmp/test
#
On Thu, 27 Apr 2017 19:32:43 +0530
Pratyush Anand wrote:
> I will implement your review comments and will send next revision.
> However, I had couple of observation which I was unable to justify:
>
> # ./trace-cmd top -s /tmp/test
> # ./trace-cmd top -p /tmp/test | grep
On Thu, 27 Apr 2017 19:32:43 +0530
Pratyush Anand wrote:
> I will implement your review comments and will send next revision.
> However, I had couple of observation which I was unable to justify:
>
> # ./trace-cmd top -s /tmp/test
> # ./trace-cmd top -p /tmp/test | grep trace-cmd
>15292
Hi Steve,
On Wednesday 26 April 2017 07:31 PM, Steven Rostedt wrote:
Sorry for the late reply. I finally have time to start looking at
trace-cmd again.
Thanks a lot for your review :-)
On Wed, 1 Mar 2017 20:32:37 +0530
Pratyush Anand wrote:
[...]
This is as nice
Hi Steve,
On Wednesday 26 April 2017 07:31 PM, Steven Rostedt wrote:
Sorry for the late reply. I finally have time to start looking at
trace-cmd again.
Thanks a lot for your review :-)
On Wed, 1 Mar 2017 20:32:37 +0530
Pratyush Anand wrote:
[...]
This is as nice idea, but it needs
Sorry for the late reply. I finally have time to start looking at
trace-cmd again.
On Wed, 1 Mar 2017 20:32:37 +0530
Pratyush Anand wrote:
> A new interface "trace-cmd top" has been introduced in this patch to
> know peak memory usage of any task.
>
> $ trace-cmd top -s
>
Sorry for the late reply. I finally have time to start looking at
trace-cmd again.
On Wed, 1 Mar 2017 20:32:37 +0530
Pratyush Anand wrote:
> A new interface "trace-cmd top" has been introduced in this patch to
> know peak memory usage of any task.
>
> $ trace-cmd top -s
> It will start to
A new interface "trace-cmd top" has been introduced in this patch to
know peak memory usage of any task.
$ trace-cmd top -s
It will start to gather statistics of all the process which will be
scheduled after this command execution.
$ trace-cmd top -p
It will print peak memory usage(in KB) against
A new interface "trace-cmd top" has been introduced in this patch to
know peak memory usage of any task.
$ trace-cmd top -s
It will start to gather statistics of all the process which will be
scheduled after this command execution.
$ trace-cmd top -p
It will print peak memory usage(in KB) against
14 matches
Mail list logo