From: Thomas Gleixner <tglx@timesys.com>
To: Martin Peschke <mp3@de.ibm.com>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-s390@vger.kernel.org, d.pensator@gmail.com,
mingo@redhat.com
Subject: Re: [RFC] [Patch 0/4] timer_stats slimmed down
Date: Sat, 14 Apr 2007 15:07:27 +0200 [thread overview]
Message-ID: <1176556047.3387.64.camel@localhost.localdomain> (raw)
In-Reply-To: <1176545387.5462.108.camel@dix>
Martin,
On Sat, 2007-04-14 at 12:09 +0200, Martin Peschke wrote:
> 2.6.21-rc* kernels come with a feature that adds timer statistics
> to /proc/timer_stats (CONFIG_TIMER_STATS). This patch set makes it use
> the proposed statistics infrastructure (-mm tree), and adds prequisite
> functions to the statistics code.
>
> The result are noticeable lines of code savings.
> kernel/time/timer_stats.c which comes with several functions which can
> be made redundant by using corresponding functions of lib/statistic.c,
> that is:
>
> - accounting
> - printing output in sequential files
> - user interface for switching accounting on/off, reset etc.
> - measuring the accounting time
> - per-cpu optimisations
>
> Function that were missing in lib/statistics, and which are added by
> this patch set, are:
>
> - allow arbitrary keys for statistics entries (e.g. structures)
> - allow client to label output of statistics entries (e.g. using keys)
>
> A secondary effect of the patch set is that we won't add another entry
> to good old /proc. The statistics infrastructure uses debugfs.
>
> This patch set is a prototype that works for me, but which might allow
> for optimisations. Suggestions are welcome.
I'm a bit short of time to take a closer look, but on the first glance
it looks good to me. I give it a whirl, when I'm back from travelling.
tglx
prev parent reply other threads:[~2007-04-14 13:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-14 10:09 [RFC] [Patch 0/4] timer_stats slimmed down Martin Peschke
2007-04-14 13:07 ` Thomas Gleixner [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=1176556047.3387.64.camel@localhost.localdomain \
--to=tglx@timesys.com \
--cc=akpm@linux-foundation.org \
--cc=d.pensator@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mp3@de.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.