From: Christoph Lameter <clameter@sgi.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SLUB: Add Kconfig option for SLAB quirks
Date: Fri, 6 Apr 2007 13:31:48 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0704061328270.23939@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20070406132634.1f64d4a1.akpm@linux-foundation.org>
On Fri, 6 Apr 2007, Andrew Morton wrote:
> urgh. It would be better to continue to rework slab/slub callers in the
> fashion which you have been doing, don't you think?
Yes definitely but I do not want to risk getting slub dropped from mm.
> Rephrasing my earlier point: are we doing things in the correct order here,
> and efficiently? It is not settled in my mind whether we want to merge
> slub _at all_. Do we have enough information yet to be able to make that
> decision?
Check the initial SLUB_V6 patch? It has long list of issues that were
addressed.
> And if that information indicates that a slub merge _is_ justified, why is
> the chosen approach superior to the incremental one: if slab code is grotty
> (it is), clean it up. If slab has unnecessary stuff, delete it.
SLUB is a fundamentally different design. We can address some of the
warts in SLAB as we do the cleanup but the basic way of handling objects
on queues is core to SLAB and is not used at all in SLUB.
prev parent reply other threads:[~2007-04-06 20:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-06 19:53 Christoph Lameter
2007-04-06 20:26 ` Andrew Morton
2007-04-06 20:31 ` 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.0704061328270.23939@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=akpm@linux-foundation.org \
--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 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®