From: Christoph Lameter <clameter@sgi.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: linux-mm@kvack.org
Subject: Re: A solution for more GFP_xx flags?
Date: Mon, 11 Sep 2006 20:01:20 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0609111957510.7923@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <45061F16.202@yahoo.com.au>
On Tue, 12 Sep 2006, Nick Piggin wrote:
> This seems like a decent approach to make a nice general interface. I guess
> existing APIs can be easily implemented by filling in the structure. If you
> took this approach I don't think there should be any objections.
>
> A minor point: would we prefer a struct argument to the allocator, or more
> function arguments? It is an API that we need to get right...
If you look at my allocator API (see the latest slab patchset), one could
add all the allocator methods into the struct in order to objectivize the
page alloator.
The logical first step towards that would be to have a struct argument
to allow detailed allocation control and to avoid this contextual
memory policy / cpuset mess.
--
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-09-12 3:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-12 2:28 Christoph Lameter
2006-09-12 2:44 ` Nick Piggin
2006-09-12 3:01 ` Christoph Lameter [this message]
2006-09-12 3:05 ` Peter Chubb
2006-09-12 3:07 ` Christoph Lameter
2006-09-12 3:11 ` Peter Chubb
2006-09-12 5:32 ` Christoph Lameter
2006-09-12 6:16 ` Paul Jackson
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.0609111957510.7923@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=linux-mm@kvack.org \
--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