From: Andrew Morton <akpm@linux-foundation.org>
To: clameter@sgi.com
Cc: linux-kernel@vger.kernel.org, Paul Mundt <lethal@linux-sh.org>
Subject: Re: [patch 1/2] From: Paul Mundt <lethal@linux-sh.org>
Date: Fri, 11 May 2007 11:39:15 -0700 [thread overview]
Message-ID: <20070511113915.267bcc66.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070511165945.913632068@sgi.com>
On Fri, 11 May 2007 09:57:50 -0700
clameter@sgi.com wrote:
> > I'll take a look at tidying up the PMB slab, getting rid of the dtor
> > shouldn't be terribly painful. I simply opted to do the list management
> > there since others were doing it for the PGD slab cache at the time that
> > was written.
>
> And here's the bit for dropping pmb_cache_dtor(), moving the list
> management up to pmb_alloc() and pmb_free().
>
> With this applied, we're all set for killing off slab destructors
> from the kernel entirely.
hm, this is already in Paul's git tree.
If we're going to slam all this into 2.6.22 then I can just tempdrop Paul's
tree.
However I think we've done enough slab work for 2.6.22 now so I'm inclined
to queue these changes for 2.6.23. That would mean that the slab changes in
-mm have a dependency on the sh git tree which I am sure to forget about.
If I end up merging these changes before Paul merges his tree, sh will
break. Presumably Paul will notice this ;)
next prev parent reply other threads:[~2007-05-11 18:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 16:57 [patch 0/2] Remove destructor support from slab allocators clameter
2007-05-11 16:57 ` [patch 1/2] From: Paul Mundt <lethal@linux-sh.org> clameter
2007-05-11 18:39 ` Andrew Morton [this message]
2007-05-12 0:22 ` Christoph Lameter
2007-05-12 1:33 ` Paul Mundt
2007-05-12 1:41 ` Andrew Morton
2007-05-11 16:57 ` [patch 2/2] Slab allocators: Drop support for destructors clameter
2007-05-11 17:55 ` Pekka Enberg
2007-05-12 1:33 ` Paul Mundt
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=20070511113915.267bcc66.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=lethal@linux-sh.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 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.