mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Lameter <clameter@sgi.com>
To: Joe Korty <joe.korty@ccur.com>
Cc: linux-kernel@vger.kernel.org, npiggin@suse.de, davem@davemloft.net
Subject: Re: [PATCH] NUMA slab allocator migration bugfix
Date: Wed, 5 Mar 2008 15:02:25 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0803051455320.4561@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20080305223314.GA4277@tsunami.ccur.com>

On Wed, 5 Mar 2008, Joe Korty wrote:

> The NUMA slab allocator (specifically, cache_alloc_refill)
> is not refreshing its local copies of what cpu and what
> numa node it is on, when it drops and reacquires the irq
> block that it inherited from its caller.  As a result
> those values become invalid if an attempt to migrate the
> process to another numa node occured while the irq block
> had been dropped.

The new slab is allocated for the node that was determined earlier and 
entered into the slab queues for that node. Howver, during the alloc we 
were rescheduled.

Then we find ourselves on another processor and recalculate the ac 
pointer. If we now retry then there is the danger of getting off node 
objects into the per cpu queue. Which may cause the wrong lock to be taken 
when draining queues. Sucks because it can cause data corruption. Same as
the other issues resolved by GFP_THISNODE.

Acked-by: Christoph Lameter <clameter@sgi.com>

Will queue it.


      reply	other threads:[~2008-03-05 23:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-05 22:33 Joe Korty
2008-03-05 23:02 ` Christoph Lameter [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=Pine.LNX.4.64.0803051455320.4561@schroedinger.engr.sgi.com \
    --to=clameter@sgi.com \
    --cc=davem@davemloft.net \
    --cc=joe.korty@ccur.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@suse.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

all inboxes | Powered by JetHome®