From: "Pekka Enberg" <penberg@cs.helsinki.fi>
To: Christoph Hellwig <hch@lst.de>
Cc: akpm@osdl.org, viro@zeniv.linux.org.uk, linux-mm@kvack.org,
Christoph Lameter <clameter@sgi.com>
Subject: Re: [PATCH 2/2] slab: optimize kmalloc_node the same way as kmalloc
Date: Fri, 4 Aug 2006 18:59:15 +0300 [thread overview]
Message-ID: <84144f020608040859o7e7b9a83p492e936af8a6e921@mail.gmail.com> (raw)
In-Reply-To: <20060804151546.GB29422@lst.de>
On 8/4/06, Christoph Hellwig <hch@lst.de> wrote:
> +static inline void *kmalloc_node(size_t size, gfp_t flags, int node)
[snip]
I think the optimization was left out on purpose as kmalloc_node() is
slow anyway. No objections from me though.
--
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>
next prev parent reply other threads:[~2006-08-04 15:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-04 15:15 Christoph Hellwig
2006-08-04 15:59 ` Pekka Enberg [this message]
2006-08-04 16:14 ` 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:
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=84144f020608040859o7e7b9a83p492e936af8a6e921@mail.gmail.com \
--to=penberg@cs.helsinki.fi \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=hch@lst.de \
--cc=linux-mm@kvack.org \
--cc=viro@zeniv.linux.org.uk \
/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