From: Christoph Lameter <clameter@sgi.com>
To: Pekka J Enberg <penberg@cs.helsinki.fi>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, hugh@veritas.com
Subject: Re: [PATCH] slab: cache_grow cleanup
Date: Tue, 9 Jan 2007 10:18:02 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0701091017350.15631@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0701091539160.10824@sbz-30.cs.Helsinki.FI>
On Tue, 9 Jan 2007, Pekka J Enberg wrote:
> The current implementation of cache_grow() has to either (1) use pre-allocated
> memory for the slab or (2) allocate the memory itself which makes the error
> paths messy. Move __GFP_NO_GROW and __GFP_WAIT processing to kmem_getpages()
> and introduce a new __cache_grow() variant that expects the memory for a new
> slab to always be handed over in the 'objp' parameter.
I am loosing track of these. What is the difference to earlier versions?
next prev parent reply other threads:[~2007-01-09 18:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 13:40 Pekka J Enberg
2007-01-09 18:18 ` Christoph Lameter [this message]
2007-01-10 7:12 ` Pekka J Enberg
2007-01-10 14:44 ` [PATCH] " Pekka Enberg
2007-01-12 9:22 ` Pekka Enberg
2007-01-28 0:12 ` Andrew Morton
2007-01-28 11:14 ` Pekka Enberg
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.0701091017350.15631@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=akpm@osdl.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/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®