linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: mel@skynet.ie (Mel Gorman)
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	npiggin@suse.de, kenchen@google.com, jschopp@austin.ibm.com,
	apw@shadowen.org, kamezawa.hiroyu@jp.fujitsu.com,
	y-goto@jp.fujitsu.com, clameter@sgi.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: -mm merge plans -- anti-fragmentation
Date: Tue, 10 Jul 2007 14:24:59 +0100	[thread overview]
Message-ID: <20070710132459.GB9426@skynet.ie> (raw)
In-Reply-To: <1184065445.5281.16.camel@lappy>

On (10/07/07 13:04), Peter Zijlstra didst pronounce:
> On Tue, 2007-07-10 at 11:20 +0100, Mel Gorman wrote:
> 
> <snip>
> 
> > > lumpy-reclaim-v4.patch
> > 
> > This patch is really what lumpy reclaim is. I believe Peter has looked
> > at this and was happy enough at the time although he is cc'd here again
> > in case this has changed. This is mainly useful with either grouping
> > pages by mobility or the ZONE_MOVABLE stuff. However, at the time the
> > patch was proposed, there was a feeling that it might help jumbo frame
> > allocation on e1000's and maybe if fsblock optimistically uses
> > contiguous pages it would have an application. I would like to see it go
> > through to see does it help e1000 at least.
> 
> I'm not seeing how this will help e1000 (and other jumbo drivers). They
> typically allocate using GFP_ATOMIC, so in order to satisfy those you'd
> need to either have a higher order watermark or do atomic defrag of the
> free space.
> 

It does help somewhat indirectly and in an unsatisfactory manner. When the
higher watermarks are breached, the atomic allocation will still succeeed
but kswapd will be poked to reclaim at a given order. This is similar to
the problems SLUB hits when it uses high-orders frequently.

-- 
Mel Gorman
Part-time Phd Student                          Linux Technology Center
University of Limerick                         IBM Dublin Software Lab

--
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:[~2007-07-10 13:24 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-10 10:20 Mel Gorman
2007-07-10 11:01 ` KAMEZAWA Hiroyuki
2007-07-10 11:12   ` Mel Gorman
2007-07-10 11:38     ` KAMEZAWA Hiroyuki
2007-07-10 15:50       ` Mel Gorman
2007-07-10 11:04 ` Peter Zijlstra
2007-07-10 13:24   ` Mel Gorman [this message]
2007-07-10 13:03 ` Nick Piggin
2007-07-10 13:55   ` Mel Gorman
2007-07-10 18:47     ` Christoph Lameter
2007-07-10 18:46   ` Christoph Lameter
2007-07-11  9:48     ` Mel Gorman
2007-07-10 14:29 ` Dave McCracken
2007-07-10 15:23   ` Nick Piggin
2007-07-10 17:11     ` Dave McCracken
2007-07-11  2:59       ` Nick Piggin
2007-07-11 10:01         ` Mel Gorman
2007-07-11 13:03         ` Andy Whitcroft
2007-07-11  8:55       ` Christoph Hellwig
2007-07-10 18:50     ` Christoph Lameter
2007-07-11 10:05       ` Mel Gorman
2007-07-12 19:29 ` Andrew Morton
2007-07-12 21:32   ` Mel Gorman
2007-07-13 15:56     ` [PATCH] Add a movablecore= parameter for sizing ZONE_MOVABLE Mel Gorman
2007-07-14  8:28       ` Nick Piggin
2007-07-14 13:02         ` Mel Gorman
2007-07-15 13:47           ` KAMEZAWA Hiroyuki
2007-07-13 10:20   ` -mm merge plans -- anti-fragmentation Andy Whitcroft
2007-07-13 16:58     ` Christoph Lameter
2007-07-13 17:02     ` Nish Aravamudan

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=20070710132459.GB9426@skynet.ie \
    --to=mel@skynet.ie \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=apw@shadowen.org \
    --cc=clameter@sgi.com \
    --cc=jschopp@austin.ibm.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=kenchen@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=npiggin@suse.de \
    --cc=y-goto@jp.fujitsu.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