From: Bill Huey (hui) <billh@gnuppy.monkey.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Martin Peschke <mp3@de.ibm.com>,
linux-kernel@vger.kernel.org, a.p.zijlstra@chello.nl,
jbaron@redhat.com, rostedt@goodmis.org,
linux-s390@vger.kernel.org,
"Bill Huey (hui)" <billh@gnuppy.monkey.org>
Subject: Re: [RFC] [Patch 4/4] lock contention tracking slimmed down
Date: Thu, 7 Jun 2007 01:56:45 -0700 [thread overview]
Message-ID: <20070607085645.GA29054@gnuppy.monkey.org> (raw)
In-Reply-To: <20070607073021.GA21139@elte.hu>
On Thu, Jun 07, 2007 at 09:30:21AM +0200, Ingo Molnar wrote:
> * Martin Peschke <mp3@de.ibm.com> wrote:
> > Do mean I might submit this stuff for -rt?
>
> Firstly, submit cleanup patches that _do not change the output_. If you
> have any output changes, do it as a separate patch, ontop of the cleanup
> patch. Mixing material changes and cleanups into a single patch is a
> basic patch submission mistake that will only earn you NACKs.
Martin,
First of all I agree with Ingo in that this needs to be seperated from
the rest of the clean ups. However, I don't understand why all of this
is so heavy weight when the current measurements that Peter makes is
completely sufficient for any reasonable purpose I can think of at the
moment. What's this stuff with labels about ?
It's important to get the points of contention so that the greater
kernel group can fix this issues and not log statistics for the purpose
of logging it. The original purpose should not be ignore when working
on this stuff.
By the way, what's the purpose of all of this stuff ? like what do you
intend to do with it over the long haul ?
bill
next prev parent reply other threads:[~2007-06-07 8:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 21:34 [RFC] [Patch 4/4] lock contention tracking slimmed down Martin Peschke
2007-06-06 23:06 ` Ingo Molnar
2007-06-07 0:17 ` Martin Peschke
2007-06-07 4:40 ` Bill Huey
2007-06-07 7:03 ` Martin Peschke
2007-06-07 7:30 ` Ingo Molnar
2007-06-07 8:56 ` Bill Huey [this message]
2007-06-11 11:26 ` Martin Peschke
2007-06-08 16:27 ` Martin Peschke
2007-06-07 6:39 ` Peter Zijlstra
2007-06-07 6:59 ` Martin Peschke
2007-06-07 7:27 ` Ingo Molnar
2007-06-08 16:07 ` Martin Peschke
2007-06-06 23:10 ` Ingo Molnar
2007-06-07 0:21 ` Martin Peschke
2007-06-07 7:44 ` Peter Zijlstra
2007-06-08 17:00 ` Martin Peschke
[not found] ` <1181322460.5728.2.camel@lappy>
[not found] ` <46698F7F.4090407@de.ibm.com>
2007-06-08 17:27 ` Peter Zijlstra
2007-06-08 17:37 ` Martin Peschke
2007-06-08 17:50 ` Peter Zijlstra
2007-06-11 10:31 ` Martin Peschke
2007-06-07 7:51 ` Peter Zijlstra
2007-06-08 17:13 ` Martin Peschke
2007-06-07 8:17 ` Peter Zijlstra
2007-06-07 10:21 ` Ingo Molnar
2007-06-11 12:20 ` Martin Peschke
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=20070607085645.GA29054@gnuppy.monkey.org \
--to=billh@gnuppy.monkey.org \
--cc=a.p.zijlstra@chello.nl \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mp3@de.ibm.com \
--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