From: Dave Hansen <haveblue@us.ibm.com>
To: Joel Schopp <jschopp@austin.ibm.com>
Cc: Paul Jackson <pj@sgi.com>, linux-mm <linux-mm@kvack.org>,
Mel Gorman <mel@csn.ul.ie>
Subject: Re: [Fwd: [PATCH 2/4] cpusets new __GFP_HARDWALL flag]
Date: Mon, 11 Jul 2005 10:49:02 -0700 [thread overview]
Message-ID: <1121104142.15095.30.camel@localhost> (raw)
In-Reply-To: <42D2AE0F.8020809@austin.ibm.com>
On Mon, 2005-07-11 at 12:36 -0500, Joel Schopp wrote:
> Dave Hansen brought this to my attention. I've attached the bit of the
> memory fragmentation avoidance you conflict with (I'm working with Mel
> on his patches). I think we share similar goals, and I wouldn't mind
> changing __GFP_USERRCLM to __GFP_USERALLOC or some neutral name we could
> share. Anything to increase the chances of fragmentation avoidance
> getting merged is good in my book.
The nice part about using __GFP_USER as the name is that it describes
how it's going to be used rather than how the kernel is going to treat
it. Somebody making a random allocator call is much more likely to know
how they're going to use it than how the kernel _should_.
-- Dave
--
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:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2005-07-11 17:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1121101013.15095.19.camel@localhost>
2005-07-11 17:36 ` Joel Schopp
2005-07-11 17:49 ` Dave Hansen [this message]
2005-07-12 2:55 ` Paul Jackson
2005-07-12 5:24 ` Dave Hansen
2005-07-12 6:11 ` Paul Jackson
2005-07-12 13:05 ` Mel Gorman
2005-07-12 20:29 ` Paul Jackson
2005-07-13 11:15 ` Mel Gorman
2005-07-14 11:06 ` Paul Jackson
2005-07-18 12:32 ` Mel Gorman
2005-07-18 20:08 ` Joel Schopp
2005-07-27 8:29 ` Paul Jackson
2005-07-27 11:10 ` Mel Gorman
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=1121104142.15095.30.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=jschopp@austin.ibm.com \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=pj@sgi.com \
/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