LKML Archive on
help / color / mirror / Atom feed
From: "Pekka J Enberg" <>
To: Andrew Morton <>
Subject: Re: slab: cache alloc cleanups
Date: Fri, 05 Jan 2007 21:59:41 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Andrew Morton writes:
> Does this actually clean things up, or does it randomly move things around
> while carefully retaining existing obscurity?  Not sure..

Heh, the bulk of it is basically splitting the current __cache_alloc into 
separate UMA and NUMA paths via __do_cache_alloc so we don't have to play 
with NUMA_BUILD tricks. I also moved __cache_alloc_node in the same 
CONFIG_NUMA block as __cache_alloc while I was at it. 


  reply	other threads:[~2007-01-05 19:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-05 11:46 [PATCH] slab: cache alloc cleanups Pekka J Enberg
2007-01-05 19:05 ` Christoph Lameter
2007-01-05 19:50 ` Andrew Morton
2007-01-05 19:59   ` Pekka J Enberg [this message]
2007-01-05 22:12   ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).