public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, andi@firstfloor.org,
	snakebyte@gmx.de, akpm@linux-foundation.org, dvhltc@us.ibm.com,
	niv@us.ibm.com, manfred@colorfullife.com, laijs@cn.fujitsu.com
Subject: Re: [PATCH] Fix rcutree grace-period-latency bug on small systems
Date: Mon, 5 Jan 2009 10:10:34 +0100	[thread overview]
Message-ID: <20090105091034.GA5440@elte.hu> (raw)
In-Reply-To: <20090105043006.GA22049@linux.vnet.ibm.com>


* Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:

> Kudos to Andi Kleen for finding a grace-period-latency problem!  The
> problem was that the special-case code for small machines never updated
> the ->signaled field to indicate that grace-period initialization had
> completed, which prevented force_quiescent_state() from ever expediting
> grace periods.  This problem resulted in grace periods extending for more
> than 20 seconds.  Not subtle.  I introduced this bug during my inspection
> process when I fixed a race between grace-period initialization and
> force_quiescent_state() execution.
> 
> The following patch properly updates the ->signaled field for the
> "small"-system case (no more than 32 CPUs for 32-bit kernels and no more
> than 64 CPUs for 64-bit kernels).
> 
> I believe that this patch should be included for 2.6.29.
> 
> Located-by: Andi Kleen <andi@firstfloor.org>
> Tested-by: Andi Kleen <andi@firstfloor.org>
> Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> ---
> 
>  rcutree.c |    1 +
>  1 file changed, 1 insertion(+)

Applied to tip/core/urgent, thanks guys!

	Ingo

      parent reply	other threads:[~2009-01-05  9:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-05  4:30 [PATCH] Fix rcutree grace-period-latency bug on small systems Paul E. McKenney
2009-01-05  5:05 ` Andi Kleen
2009-01-05  9:10 ` Ingo Molnar [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=20090105091034.GA5440@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=dvhltc@us.ibm.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    --cc=niv@us.ibm.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=snakebyte@gmx.de \
    /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