linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andy Whitcroft <apw@shadowen.org>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Andy Whitcroft <apw@shadowen.org>, Mel Gorman <mel@csn.ul.ie>
Subject: [PATCH 0/3] Lumpy Reclaim V6
Date: Fri, 20 Apr 2007 16:03:03 +0100	[thread overview]
Message-ID: <exportbomb.1177081388@pinky> (raw)

Following this email are three patches to the lumpy reclaim
algorithm.  These apply on top of the lumpy patches in 2.6.21-rc6-mm1
(lumpy V5); making lumpy V6.  The first enables kswapd to apply
reclaim at the order of the allocations which trigger background
reclaim.  The second increases pressure on the area at the end of
the inactive list.  The last introduces a new symbolic constant
representing the boundary between easily reclaimed areas and those
where extra pressure is applicable.  Andrew, please consider for -mm.

Comparitive testing between lumpy-V5 and lumpy-V6 shows a
considerable improvement when under extreme load.  lumpy-V5 relies on
the pages in an area being rotated onto the inactive list together
and remaining inactive long enough to be reclaimed from that list.
Under high load a significant portion of the pages return to active
or are referenced before this can occur.  Lumpy-V6 targets all
LRU pages in the area greatly increasing the chance of reclaiming
it completely.

kswapd-use-reclaim-order-in-background-reclaim: When an allocator
  has to dip below the low water mark for a zone, kswapd is awoken
  to start background reclaim.  Make kswapd use the highest order
  of these allocations to define the order at which it reclaims.

lumpy-increase-pressure-at-the-end-of-the-inactive-list: when
  reclaiming at higher order target all pages in the contigious
  area for reclaim, including active and recently referenced pages.
  This increases the chances of that area becoming free.

introduce-HIGH_ORDER-delineating-easily-reclaimable-orders:
  The memory allocator treats lower and higher order allocations
  slightly differently.  Lumpy reclaim also changes behaviour at
  this same boundary.  Pull out the magic numbers and replace them
  with a symbolic constant.

Against: 2.6.21-rc6-mm1

-apw

Changes in lumpy V5:

   Andy Whitcroft:
      lumpy: back out removal of active check in isolate_lru_pages
      lumpy: only count taken pages as scanned

Changes in lumpy V4:

   Andy Whitcroft:
      lumpy: isolate_lru_pages wants to specifically take active
						      or inactive pages
      lumpy: ensure that we compare PageActive and active safely
      lumpy: update commentry on subtle comparisons and rounding assumptions
      lumpy: only check for valid pages when holes are present

Changes in lumpy V3:

   Adrian Bunk:
      lumpy-reclaim-cleanup

   Andrew Morton:
      lumpy-reclaim-v2-page_to_pfn-fix
      lumpy-reclaim-v2-tidy

   Andy Whitcroft:
      lumpy: ensure we respect zone boundaries
      lumpy: take the other active/inactive pages in the area

--
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-04-20 15:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-20 15:03 Andy Whitcroft [this message]
2007-04-20 15:03 ` [PATCH 1/3] kswapd: use reclaim order in background reclaim Andy Whitcroft
2007-04-20 15:04 ` [PATCH 2/3] lumpy: increase pressure at the end of the inactive list Andy Whitcroft
2007-04-21  8:24   ` Andrew Morton
2007-04-20 15:04 ` [PATCH 3/3] introduce HIGH_ORDER delineating easily reclaimable orders Andy Whitcroft
2007-04-21  8:28   ` Andrew Morton
2007-04-21  8:32     ` Andrew Morton
2007-04-23 10:23       ` Andy Whitcroft

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=exportbomb.1177081388@pinky \
    --to=apw@shadowen.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --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