From: Soeren Sandmann <sandmann@daimi.au.dk>
To: bert hubert <bert.hubert@netherlabs.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Announce: Sysprof 1.0 -- a sampling, systemwide Linux profiler
Date: 18 Sep 2005 00:05:15 +0200 [thread overview]
Message-ID: <ye8slw38i5g.fsf@horse06.daimi.au.dk> (raw)
In-Reply-To: <20050917211656.GA27448@outpost.ds9a.nl>
bert hubert <bert.hubert@netherlabs.nl> writes:
> How is this different from oprofile?
>
> Looks like you did an exact, but less capable, reimplementation.
The kernel module is indeed less capable by itself, but the userspace
tools are a lot easier to use and show you significantly more
details. Oprofile may have improved since then, but when I started
sysprof:
- oprofile didn't work on anything but smp kernels
- oprofile could not produce callgraph information without not only
recompiling my kernel, but also patching the kernel
- oprofile had a user interface that I simply didn't understand. As I
remember it, I had to know about performance counters and how to
translate those into binary masks
Contrast with sysprof, where you
- insert the module
- hit the start button
- do the thing you want to profile
- hit the profile button
and you get data presented in a way that is just a whole lot more
useful than the flat text files generated by oprofile.
Søren
next prev parent reply other threads:[~2005-09-17 22:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-17 21:05 Soeren Sandmann
2005-09-17 21:16 ` John Levon
2005-09-17 21:16 ` bert hubert
2005-09-17 22:05 ` Soeren Sandmann [this message]
2005-09-17 22:20 ` John Levon
2005-09-17 23:03 ` Soeren Sandmann
2005-09-18 0:25 ` Anton Blanchard
2005-09-17 23:28 ` Tomasz Torcz
2005-09-17 23:53 ` John Levon
2005-09-18 8:45 ` bert hubert
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=ye8slw38i5g.fsf@horse06.daimi.au.dk \
--to=sandmann@daimi.au.dk \
--cc=bert.hubert@netherlabs.nl \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®