lkml.org 
[lkml]   [1999]   [Nov]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: Profiling timer not delivered during syscalls?
From
Date
patl@cag.lcs.mit.edu (Patrick J. LoPresti) writes:

|> mcount() generates the call graph; I am talking about the statistical
|> sampling provided by the profiling timer. I understand why system
|> calls are not sampled, but I am not sure I like it. High-latency
|> system calls can have a big effect on an application's performance.
|> If your application is slow because it makes too many slow system
|> calls, there does not seem to be any easy way to find that out; the
|> results of gprof can even be misleading.

gprof is not for profiling the kernel. Only user time is counted.

Andreas.

--
Andreas Schwab "And now for something
SuSE Labs completely different."
schwab@suse.de
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:54    [W:0.052 / U:1.968 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site