From: Christoph Lameter <clameter@sgi.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, mpm@selenic.com
Subject: Re: [SLUB 0/3] SLUB: The unqueued slab allocator V5
Date: Sat, 10 Mar 2007 23:04:44 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0703102259440.23001@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20070310224946.f9385917.akpm@linux-foundation.org>
On Sat, 10 Mar 2007, Andrew Morton wrote:
> Is this safe to think about applying yet?
Its safe. By default kernels will be build with SLAB. SLUB becomes only a
selectable alternative. It should not become the primary slab until we
know that its really superior overall and have thoroughly tested it in
a variety of workloads.
> We lost the leak detector feature.
There will be numerous small things that will have to be addressed. There
is also some minor work to be done for tracking callers better.
> It might be nice to create synonyms for PageActive, PageReferenced and
> PageError, to make things clearer in the slub core. At the expense of
> making things less clear globally. Am unsure.
I have been back and forth on doing that. There are somewhat similar
in what they mean for SLUB. But creating synonyms may be confusing to
those checking how page flags are being used.
--
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>
prev parent reply other threads:[~2007-03-11 7:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-11 2:10 Christoph Lameter
2007-03-11 2:10 ` [SLUB 1/3] SLUB core Christoph Lameter
2007-03-11 2:10 ` [SLUB 2/3] Enable poisoning for RCU and constructors Christoph Lameter
2007-03-11 2:10 ` [SLUB 3/3] Configurable slub_max_order Christoph Lameter
2007-03-11 6:49 ` [SLUB 0/3] SLUB: The unqueued slab allocator V5 Andrew Morton
2007-03-11 7:04 ` 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.0703102259440.23001@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.com \
/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