From: Christoph Lameter <clameter@sgi.com>
To: Paul Mundt <lethal@linux-sh.org>
Cc: Matt Mackall <mpm@selenic.com>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org
Subject: Re: [PATCH] slob: poor man's NUMA, take 5.
Date: Fri, 15 Jun 2007 07:31:36 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0706150730530.7400@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20070615053906.GA28865@linux-sh.org>
On Fri, 15 Jun 2007, Paul Mundt wrote:
> The comments moved because the kmalloc() definition moved, it didn't seem
> entirely helpful to leave the comment by itself and have the definitions
> in the *_def.h files.
That is helpful because someone will be first looking at slab.h to find
the general API. The description is not SLAB, SLUB or SLOB specific.
> But I'll try and generalize the comments regarding the allocator gfp
> flags, and keep those in slab.h, so it's more obvious (as well as tidying
> them for correctness).
Great.
--
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:[~2007-06-15 14:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-15 3:34 Paul Mundt
2007-06-15 4:30 ` Christoph Lameter
2007-06-15 5:39 ` Paul Mundt
2007-06-15 14:31 ` Christoph Lameter [this message]
2007-06-15 6:44 ` Matt Mackall
2007-06-15 8:22 ` Paul Mundt
2007-06-15 14:39 ` Christoph Lameter
2007-06-18 2:39 ` Paul Mundt
2007-06-19 3:52 ` Paul Mundt
2007-06-19 3:57 ` Matt Mackall
2007-06-19 4:01 ` 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=Pine.LNX.4.64.0706150730530.7400@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=lethal@linux-sh.org \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.com \
--cc=nickpiggin@yahoo.com.au \
/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