linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: jschopp@austin.ibm.com, linux-mm@kvack.org, mel@csn.ul.ie
Subject: Re: [Fwd: [PATCH 2/4] cpusets new __GFP_HARDWALL flag]
Date: Mon, 11 Jul 2005 23:11:50 -0700	[thread overview]
Message-ID: <20050711231150.4d72c8a3.pj@sgi.com> (raw)
In-Reply-To: <1121145895.5446.1.camel@localhost>

Dave wrote:
> four types ==> two GFP bits

Ok.  Guess I should read the patch to figure out
what these 4 types are (and which subsets thereof
map to my 2 types USER and !USER aka KERN.)

If there is not a surjective function from your
4 types to my 2 types, then I can't so easily
share your GFP bits.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.925.600.0401
--
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>

  reply	other threads:[~2005-07-12  6:11 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
2005-07-12  2:55   ` Paul Jackson
2005-07-12  5:24     ` Dave Hansen
2005-07-12  6:11       ` Paul Jackson [this message]
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=20050711231150.4d72c8a3.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=haveblue@us.ibm.com \
    --cc=jschopp@austin.ibm.com \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    /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