All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Simon.Derr@bull.net, clameter@sgi.com, rohit.seth@intel.com
Subject: Re: [PATCH 03/05] mm rationalize __alloc_pages ALLOC_* flag names
Date: Tue, 15 Nov 2005 11:20:42 -0800	[thread overview]
Message-ID: <20051115112042.253ca3cf.pj@sgi.com> (raw)
In-Reply-To: <4379B0A7.3090803@yahoo.com.au>

Nick suggested:
> ALLOC_DIP_NONE
> ALLOC_DIP_LESS
> ALLOC_DIP_MORE
> ALLOC_DIP_FULL

Sweet.  PATCH coming soon.

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

WARNING: multiple messages have this Message-ID (diff)
From: Paul Jackson <pj@sgi.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Simon.Derr@bull.net, clameter@sgi.com, rohit.seth@intel.com
Subject: Re: [PATCH 03/05] mm rationalize __alloc_pages ALLOC_* flag names
Date: Tue, 15 Nov 2005 11:20:42 -0800	[thread overview]
Message-ID: <20051115112042.253ca3cf.pj@sgi.com> (raw)
In-Reply-To: <4379B0A7.3090803@yahoo.com.au>

Nick suggested:
> ALLOC_DIP_NONE
> ALLOC_DIP_LESS
> ALLOC_DIP_MORE
> ALLOC_DIP_FULL

Sweet.  PATCH coming soon.

-- 
                  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:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2005-11-15 19:20 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-14  4:03 [PATCH 01/05] mm fix __alloc_pages cpuset ALLOC_* flags Paul Jackson
2005-11-14  4:03 ` Paul Jackson
2005-11-14  4:03 ` [PATCH 02/05] mm simplify " Paul Jackson
2005-11-14  4:03   ` Paul Jackson
2005-11-14  4:03 ` [PATCH 03/05] mm rationalize __alloc_pages ALLOC_* flag names Paul Jackson
2005-11-14  4:03   ` Paul Jackson
2005-11-15  9:00   ` Nick Piggin
2005-11-15  9:00     ` Nick Piggin
2005-11-15  9:03     ` Andrew Morton
2005-11-15  9:03       ` Andrew Morton
2005-11-15  9:55       ` Nick Piggin
2005-11-15  9:55         ` Nick Piggin
2005-11-15 19:20         ` Paul Jackson [this message]
2005-11-15 19:20           ` Paul Jackson
2005-11-15  9:59       ` Arjan van de Ven
2005-11-15  9:59         ` Arjan van de Ven
2005-11-15  9:18     ` Paul Jackson
2005-11-15  9:18       ` Paul Jackson
2005-11-14  4:04 ` [PATCH 04/05] mm simplify __alloc_pages cpuset hardwall logic Paul Jackson
2005-11-14  4:04   ` Paul Jackson
2005-11-14  4:04 ` [PATCH 05/05] mm GFP_ATOMIC comment Paul Jackson
2005-11-14  4:04   ` Paul Jackson
2005-11-15  8:52 ` [PATCH 01/05] mm fix __alloc_pages cpuset ALLOC_* flags Nick Piggin
2005-11-15  8:52   ` Nick Piggin
2005-11-15  9:50   ` Paul Jackson
2005-11-15  9:50     ` 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=20051115112042.253ca3cf.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=Simon.Derr@bull.net \
    --cc=akpm@osdl.org \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=rohit.seth@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.