From: Karim Yaghmour <karym@opersys.com>
To: John Levon <moz@compsoc.man.ac.uk>
Cc: linux-kernel@vger.kernel.org, linuxperf@nl.linux.org
Subject: Re: [ANNOUNCE] oprofile profiler
Date: Thu, 11 Jan 2001 05:27:43 -0500 [thread overview]
Message-ID: <3A5D8B10.D244D58F@opersys.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0101101813160.4135-100000@mrworry.compsoc.man.ac.uk>
Hello John,
This is really interesting. Great stuff.
As Alan had once suggested, it would be very interesting to have this
information correlated with the content of the traces collected using
the Linux Trace Toolkit (www.opersys.com/LTT). For instance, you could see
how many cache faults the read() or write() operation of your application
generated and other unique info. It would also be possible to enhance
the post-mortem analysis done by LTT to take in account this data.
You could also use LTT's dynamic event creation mechanism to log the
profiling data as part of the trace.
There are definitely opportunities for interfacing/integrating here.
Let me know what you think.
Best regards
Karim
John Levon wrote:
>
> oprofile is a low-overhead statistical profiler capable of
> instruction-grain profiling of the kernel (including interrupt handlers),
> modules, and user-space libraries and binaries.
>
> It uses the Intel P6 performance counters as a source of interrupts to
> trigger the accounting handler in a manner similar to that of Digital's
> DCPI. All running processes, and the kernel, are profiled by default. The
> profiles can be extracted at any time with a simple utility. The system
> consists of a kernel module and a simple background daemon.
>
> Typical overhead is around 3 or 4 percent. Worst case overhead on a
> Pentium II 350 UP system is around 10-15%
>
> You can read a little more about oprofile, and download a very alpha
> version at :
>
> http://oprofile.sourceforge.net/
>
> oprofile is released under the GNU GPL.
>
> thanks
> john
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
--
===================================================
Karim Yaghmour
karym@opersys.com
Operating System Consultant
(Linux kernel, real-time and distributed systems)
===================================================
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-01-11 10:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-10 18:23 [ANNOUNCE] oprofile profiler John Levon
2001-01-11 10:27 ` Karim Yaghmour [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A5D8B10.D244D58F@opersys.com \
--to=karym@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxperf@nl.linux.org \
--cc=moz@compsoc.man.ac.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox