public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] RCU changes for v2.6.38
Date: Fri, 7 Jan 2011 00:32:41 -0800	[thread overview]
Message-ID: <20110107083240.GN2506@linux.vnet.ibm.com> (raw)
In-Reply-To: <20110106235457.GB15940@elte.hu>

On Fri, Jan 07, 2011 at 12:54:57AM +0100, Ingo Molnar wrote:
> 
> * Linus Torvalds <torvalds@linux-foundation.org> wrote:
> 
> > On Thu, Jan 6, 2011 at 1:08 AM, Ingo Molnar <mingo@elte.hu> wrote:
> > >
> > > Please pull the latest core-rcu-for-linus git tree from:
> > 
> > So I pulled, but I'm not convinced about the crazy busy-looping
> > SRCU_SYNCHRONIZE_DELAY thing.
> > 
> > Why does it do a silly udelay(), instead of just looping over the
> > srcu_readers_active_idx() for a few times? You're wasting CPU time
> > anyway, why ask the user how many usecs to waste?
> > 
> > IOW, why isn't that "wait for no active readers" a nice helper
> > function, and why doesn't it do
> > 
> >    for (i = 0; i < CONFIG_SRCU_SYNCHRONIZE_DELAY; i++) {
> >       if (!srcu_readers_active_idx(sp, idx))
> >          return;
> >       udelay(1);
> >    }
> >    while (srcu_readers_active_idx(sp, idx))
> >       schedule_timeout_interruptible(1);
> > 
> > instead? And is it really sane to ask the kernel configurator to come
> > up with a random value (ie that "CONFIG_SRCU_SYNCHRONIZE_DELAY" is
> > just stupid and wrong)?
> > 
> > Please fix this. And don't make people answer unanswerable questions.
> > If YOU and Paul don't know the answer, why the hell do you expect
> > somebody who does a "make config" to know the answer?
> > 
> > Either pick a number, or pick an algorithm that self-tunes.
> > 
> > Don't use the Kconfig system as a way to tell people that it's their
> > fault when you made a bad decision. Really.
> 
> Fully agreed - we'll fix this.

I am on it!

							Thanx, Paul

      reply	other threads:[~2011-01-07  8:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-06  9:08 [GIT PULL] RCU changes for v2.6.38 Ingo Molnar
2011-01-06 18:16 ` Linus Torvalds
2011-01-06 23:54   ` Ingo Molnar
2011-01-07  8:32     ` Paul E. McKenney [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=20110107083240.GN2506@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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