From: Martin Peschke <mp3@de.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: a.p.zijlstra@chello.nl, jbaron@redhat.com, rostedt@goodmis.org,
billh@gnuppy.monkey.org, mingo@elte.hu,
linux-s390@vger.kernel.org
Subject: [RFC] [Patch 0/4] lock contention tracking slimmed down
Date: Wed, 06 Jun 2007 23:33:22 +0200 [thread overview]
Message-ID: <1181165602.7133.18.camel@dix> (raw)
We can save many lines of code in the lock contention tracking patches
by using some common code which implements statistics in a generic way.
Data is still gathered per cpu; output goes to debugfs files. Several
ideas that went into the lock contention tracking patches can be found
in the statistics infrastructure as well.
Please see the last patch for details and for some sample output.
The first three patches just prepare the statistics infrastructure
for this new use case.
Feel free to pick at any rough edge you want me to smooth out,
if you are interested in this approach.
[Patch 1/4] statistics: no include hell for users
[Patch 2/4] statistics: cleanups
[Patch 3/4] statistics: sets of statistics in single file
[Patch 4/4] lock contention tracking slimmed down
Please mind that the patches are against 2.6.22-rc3-mm1. They don't apply
against 2.6.22-rc4-mm1. (The statistics library functions have been dropped,
because a couple more users would be nice.)
Ah, and you might need to add CONFIG_STATISTICS to Kconfig of the
architecture of your choice (see s390).
Signed-off-by: Martin Peschke <mp3@de.ibm.com>
reply other threads:[~2007-06-06 21:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1181165602.7133.18.camel@dix \
--to=mp3@de.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=billh@gnuppy.monkey.org \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).