All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: npiggin@suse.de, stable@kernel.org, linux-mm@kvack.org,
	Christoph Lameter <cl@linux.com>,
	akpm@linux-foundation.org
Subject: Re: [patch 1/3] mm: SLUB fix reclaim_state
Date: Wed, 6 May 2009 11:34:41 -0500	[thread overview]
Message-ID: <20090506163440.GV31071@waste.org> (raw)
In-Reply-To: <1241594430.15411.3.camel@penberg-laptop>

On Wed, May 06, 2009 at 10:20:30AM +0300, Pekka Enberg wrote:
> On Tue, 2009-05-05 at 19:13 +1000, npiggin@suse.de wrote:
> > plain text document attachment (mm-slub-fix-reclaim_state.patch)
> > SLUB does not correctly account reclaim_state.reclaimed_slab, so it will
> > break memory reclaim. Account it like SLAB does.
> > 
> > Cc: stable@kernel.org
> > Cc: linux-mm@kvack.org
> > Cc: Pekka Enberg <penberg@cs.helsinki.fi>
> > Cc: Matt Mackall <mpm@selenic.com>
> > Cc: Christoph Lameter <cl@linux.com>
> > Signed-off-by: Nick Piggin <npiggin@suse.de>
> 
> I have applied the patch series. I see you have cc'd stable so I assume
> you want this in 2.6.30, right? This seems like a rather serious bug but
> I wonder why we've gotten away with it for so long? Is there a test
> program or a known workload that breaks without this?

Appears to me to be less a correctness than a balancing issue. reclaim
state is a back channel into the shrink code that says 'yes, this is
working'. Without it, things should still work, but possibly not as
smoothly.

-- 
Mathematics is the supreme nostalgia of our time.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2009-05-06 16:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090505091343.706910164@suse.de>
2009-05-05  9:13 ` [patch 1/3] mm: SLUB fix reclaim_state npiggin
2009-05-05 13:46   ` Christoph Lameter
2009-05-06  7:20   ` Pekka Enberg
2009-05-06 13:29     ` Christoph Lameter
2009-05-06 13:42     ` Nick Piggin
2009-05-07  8:50       ` Pekka Enberg
2009-05-06 16:02     ` Johannes Weiner
2009-05-06 16:34     ` Matt Mackall [this message]
2009-05-05  9:13 ` [patch 2/3] mm: SLOB " npiggin
2009-05-05 13:47   ` Christoph Lameter
2009-05-05 16:47   ` Matt Mackall
2009-05-05  9:13 ` [patch 3/3] mm: SLQB " npiggin
2009-05-05 13:47   ` Christoph Lameter

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=20090506163440.GV31071@waste.org \
    --to=mpm@selenic.com \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --cc=linux-mm@kvack.org \
    --cc=npiggin@suse.de \
    --cc=penberg@cs.helsinki.fi \
    --cc=stable@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.