linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: Mel Gorman <mel@csn.ul.ie>
Cc: linux-mm@kvack.org, nickpiggin@yahoo.com.au, ak@suse.de,
	linux-kernel@vger.kernel.org, lhms-devel@lists.sourceforge.net,
	mingo@elte.hu
Subject: Re: [PATCH 1/5] Light fragmentation avoidance without usemap: 001_antidefrag_flags
Date: Tue, 22 Nov 2005 19:45:13 -0800	[thread overview]
Message-ID: <20051122194513.3883d135.pj@sgi.com> (raw)
In-Reply-To: <20051122191715.21757.82818.sendpatchset@skynet.csn.ul.ie>

+#define __GFP_EASYRCLM   ((__force gfp_t)0x40000u) /* Easily reclaimed page */

Acked (this one line) by pj <grin>.

-- 
                  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-23  3:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-22 19:17 [PATCH 0/5] Light fragmentation avoidance without usemap Mel Gorman
2005-11-22 19:17 ` [PATCH 1/5] Light fragmentation avoidance without usemap: 001_antidefrag_flags Mel Gorman
2005-11-23  3:45   ` Paul Jackson [this message]
2005-11-22 19:17 ` [PATCH 2/5] Light fragmentation avoidance without usemap: 002_fragcore Mel Gorman
2005-11-22 19:17 ` [PATCH 3/5] Light fragmentation avoidance without usemap: 003_percpu Mel Gorman
2005-11-22 19:17 ` [PATCH 4/5] Light fragmentation avoidance without usemap: 004_configurable Mel Gorman
2005-11-22 19:17 ` [PATCH 5/5] Light fragmentation avoidance without usemap: 005_drainpercpu 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=20051122194513.3883d135.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=ak@suse.de \
    --cc=lhms-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    --cc=mingo@elte.hu \
    --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