All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 0/6] Per cpu structures for SLUB
Date: Thu, 23 Aug 2007 11:52:04 +0200	[thread overview]
Message-ID: <1187862724.6114.356.camel@twins> (raw)
In-Reply-To: <20070823064653.081843729@sgi.com>

Hi,

while I like this patch set I'm at odds with the interaction of this and
making the alloc/free fast paths lockless. 

The main race is s->cpu_slab[] and c->freelist. How does one close that
gap?

(btw, have you looked at my -rt slub patch?)


  parent reply	other threads:[~2007-08-23  9:52 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-23  6:46 [patch 0/6] Per cpu structures for SLUB Christoph Lameter
2007-08-23  6:46 ` Christoph Lameter
2007-08-23  6:46 ` [patch 1/6] SLUB: Avoid page struct cacheline bouncing due to remote frees to cpu slab Christoph Lameter
2007-08-23  6:46   ` Christoph Lameter
2007-08-23  6:46 ` [patch 2/6] SLUB: Do not use page->mapping Christoph Lameter
2007-08-23  6:46   ` Christoph Lameter
2007-08-23  6:46 ` [patch 3/6] SLUB: Move page->offset to kmem_cache_cpu->offset Christoph Lameter
2007-08-23  6:46   ` Christoph Lameter
2007-08-23  6:46 ` [patch 4/6] SLUB: Avoid touching page struct when freeing to per cpu slab Christoph Lameter
2007-08-23  6:46   ` Christoph Lameter
2007-08-23 15:05   ` Peter Zijlstra
2007-08-23 19:30     ` Christoph Lameter
2007-08-24 16:46       ` Christoph Lameter
2007-08-23  6:46 ` [patch 5/6] SLUB: Place kmem_cache_cpu structures in a NUMA aware way Christoph Lameter
2007-08-23  6:46   ` Christoph Lameter
2007-08-23  6:46 ` [patch 6/6] SLUB: Optimize cacheline use for zeroing Christoph Lameter
2007-08-23  6:46   ` Christoph Lameter
2007-08-23  9:52 ` Peter Zijlstra [this message]
2007-08-23 19:25   ` [patch 0/6] Per cpu structures for SLUB Christoph Lameter
2007-08-24 21:38 ` Andrew Morton
2007-08-24 21:38   ` Andrew Morton
2007-08-27 18:50   ` Christoph Lameter
2007-08-27 18:50     ` Christoph Lameter
2007-08-27 23:51     ` Andrew Morton
2007-08-27 23:51       ` Andrew Morton

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=1187862724.6114.356.camel@twins \
    --to=peterz@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.