From: Soeren Sandmann <sandmann@daimi.au.dk>
To: Ingo Molnar <mingo@elte.hu>
Cc: Christoph Hellwig <hch@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: Announce: Sysprof 1.1.2 CPU profiler for Linux
Date: 13 Oct 2009 22:13:54 +0200 [thread overview]
Message-ID: <ye8pr8r59x9.fsf@camel23.daimi.au.dk> (raw)
In-Reply-To: <20091012205812.GF17163@elte.hu>
Ingo Molnar <mingo@elte.hu> writes:
> * Christoph Hellwig <hch@infradead.org> wrote:
>
> > On Sat, Sep 26, 2009 at 05:46:23PM +0200, Soeren Sandmann wrote:
> > > Sysprof 1.1.2 is now available. This is a development release leading
> > > up to a stable 1.2.0 release.
> > >
> > > Sysprof is a sampling system-wide CPU profiler for Linux. This
> > > version is based on the perf counter interface in 2.6.31 kernels and
> > > will not work with earlier kernels.
> >
> > Btw, what is the plan for the sysprof ftrace plugin? In general we
> > move away from ftrace plugins towards trace events and perf, and if I
> > remember correctly ftrace file format changes caused enough pain for
> > sysprof that it kept shipping it's old hacky kernel module.
Missed this mail somehow. The main issue with the ftrace plugin was
performance. Often, 20% of the time, as reported by sysprof was spent
in the ftrace read() interface. I think some of that came from the
locking code compiled with debug information, but even without that,
there was significant overhead.
The perf counter interface works very well and will eventually allow a
number of new features to be added.
> > Is it time to deprectate the sysprof ftrace plugin?
>
> Yes - but it's minimal maintenance overhead so we want to keep it for
> kernel release or two, to sunset it properly.
Makes sense to me.
Thanks,
Soren
next prev parent reply other threads:[~2009-10-13 20:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-26 15:46 Soeren Sandmann
2009-10-06 15:07 ` Christoph Hellwig
2009-10-12 20:58 ` Ingo Molnar
2009-10-13 20:13 ` Soeren Sandmann [this message]
2009-10-25 7:51 ` Christoph Hellwig
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=ye8pr8r59x9.fsf@camel23.daimi.au.dk \
--to=sandmann@daimi.au.dk \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®