> syscall nr and pid at minimum then.
oprofile already supports logging the pid I believe. Otherwise
the pid filter in opreport could hardly work.
> Still doesn't work for modules either.
oprofile works fine for modules.
>
> what it ends up doing is using an entirely different interface for
>
Andi Kleen wrote:
another thing that the current profiling can't do, is to show what the
system is doing
when it hits the latency.. so someone calling fsync() will show up in the
waiting for
IO function, but not that it was due to an fsync().
Hmm so how about extending oprofile to always log
On Sat, Jan 19, 2008 at 06:33:30AM +0100, Andi Kleen wrote:
> > another thing that the current profiling can't do, is to show what the
> > system is doing
> > when it hits the latency.. so someone calling fsync() will show up in the
> > waiting for
> > IO function, but not that it was due to an f
> another thing that the current profiling can't do, is to show what the
> system is doing
> when it hits the latency.. so someone calling fsync() will show up in the
> waiting for
> IO function, but not that it was due to an fsync().
Hmm so how about extending oprofile to always log the syscall
Andi Kleen wrote:
yes indeed; I sort of use the same infrastructure inside the scheduler; the
biggest
reason I felt I had to do something different was that I wanted to do per
process
data collection, so that you can see for a specific process what was going
on.
Wouldn't it have been easier t
> yes indeed; I sort of use the same infrastructure inside the scheduler; the
> biggest
> reason I felt I had to do something different was that I wanted to do per
> process
> data collection, so that you can see for a specific process what was going
> on.
Wouldn't it have been easier then to j
Andi Kleen wrote:
Arjan van de Ven <[EMAIL PROTECTED]> writes:
The Intel Open Source Technology Center is pleased to announce the
release of version 0.1 of LatencyTOP, a tool for developers to visualize
system latencies.
Just for completeness -- Linux already had a way to profile latencies
si
Arjan van de Ven <[EMAIL PROTECTED]> writes:
> The Intel Open Source Technology Center is pleased to announce the
> release of version 0.1 of LatencyTOP, a tool for developers to visualize
> system latencies.
Just for completeness -- Linux already had a way to profile latencies
since quite some t
On Fri, 2008-01-18 at 09:36 -0800, Arjan van de Ven wrote:
> The Intel Open Source Technology Center is pleased to announce the
> release of version 0.1 of LatencyTOP, a tool for developers to visualize
> system latencies.
>
> http://www.latencytop.org
>
> Slow servers, Skipping audio, Jerky vid
At 18.36 18/01/2008, Arjan van de Ven wrote:
>The Intel Open Source Technology Center is pleased to announce the
>release of version 0.1 of LatencyTOP, a tool for developers to visualize
>system latencies.
>
>http://www.latencytop.org
>
[...snip...]
>
>The most basic annotation looks like this (i
At 19.35 18/01/2008, Arjan van de Ven wrote:
>Roberto Fichera wrote:
>> At 18.36 18/01/2008, Arjan van de Ven wrote:
>>> The Intel Open Source Technology Center is pleased to announce the
>>> release of version 0.1 of LatencyTOP, a tool for developers to visualize
>>> system latencies.
>>>
>>> http
Roberto Fichera wrote:
At 18.36 18/01/2008, Arjan van de Ven wrote:
The Intel Open Source Technology Center is pleased to announce the
release of version 0.1 of LatencyTOP, a tool for developers to visualize
system latencies.
http://www.latencytop.org
[...snip...]
The most basic annotation
The Intel Open Source Technology Center is pleased to announce the
release of version 0.1 of LatencyTOP, a tool for developers to visualize
system latencies.
http://www.latencytop.org
Slow servers, Skipping audio, Jerky video --everyone knows the symptoms
of latency. But to know what's really go
13 matches
Mail list logo
