linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mel Gorman <mel@csn.ul.ie>
To: Mel Gorman <mel@csn.ul.ie>,
	Linux Memory Management List <linux-mm@kvack.org>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
	Rik van Riel <riel@redhat.com>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	Christoph Lameter <cl@linux-foundation.org>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Nick Piggin <npiggin@suse.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Lin Ming <ming.m.lin@intel.com>,
	Zhang Yanmin <yanmin_zhang@linux.intel.com>,
	Peter Zijlstra <peterz@infradead.org>
Subject: [PATCH 00/26] Cleanup and optimise the page allocator V4
Date: Mon, 16 Mar 2009 17:53:14 +0000	[thread overview]
Message-ID: <1237226020-14057-1-git-send-email-mel@csn.ul.ie> (raw)

Here is V4 of the cleanup and optimisation of the page allocator and it
should be ready for general testing. The main difference from V3 is that the
controversial patches have been dropped and I'll revisit them later. Tests
are currently running to I have exact figures of how things stand on the
test machines I used but I think this can be considered a merge candidate,
possibly for 2.6.30 depending on how reviews and wider testing goes.

Changes since V3
  o Drop the more controversial patches for now and focus on the "obvious win"
    material
  o Add reviewed-by notes
  o Fix changelog entry to say __rmqueue_fallback instead __rmqueue
  o Add unlikely() for the clearMlocked check
  o Change where PGFREE is accounted in free_hot_cold_page() to have symmetry
    with __free_pages_ok()

Changes since V2
  o Remove brances by treating watermark flags as array indices
  o Remove branch by assuming __GFP_HIGH == ALLOC_HIGH
  o Do not check for compound on every page free
  o Remove branch by always ensuring the migratetype is known on free
  o Simplify buffered_rmqueue further
  o Reintroduce improved version of batched bulk free of pcp pages
  o Use allocation flags as an index to zone watermarks
  o Work out __GFP_COLD only once
  o Reduce the number of times zone stats are updated
  o Do not dump reserve pages back into the allocator. Instead treat them
    as MOVABLE so that MIGRATE_RESERVE gets used on the max-order-overlapped
    boundaries without causing trouble
  o Allow pages up to PAGE_ALLOC_COSTLY_ORDER to use the per-cpu allocator.
    order-1 allocations are frequently enough in particular to justify this
  o Rearrange inlining such that the hot-path is inlined but not in a way
    that increases the text size of the page allocator
  o Make the check for needing additional zonelist filtering due to NUMA
    or cpusets as light as possible
  o Do not destroy compound pages going to the PCP lists
  o Delay the merging of buddies until a high-order allocation needs them
    or anti-fragmentation is being forced to fallback

Changes since V1
  o Remove the ifdef CONFIG_CPUSETS from inside get_page_from_freelist()
  o Use non-lock bit operations for clearing the mlock flag
  o Factor out alloc_flags calculation so it is only done once (Peter)
  o Make gfp.h a bit prettier and clear-cut (Peter)
  o Instead of deleting a debugging check, replace page_count() in the
    free path with a version that does not check for compound pages (Nick)
  o Drop the alteration for hot/cold page freeing until we know if it
    helps or not

--
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:[~2009-03-16 17:51 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-16 17:53 Mel Gorman [this message]
2009-03-16 17:53 ` [PATCH 01/27] Replace __alloc_pages_internal() with __alloc_pages_nodemask() Mel Gorman
2009-03-16 17:53 ` [PATCH 02/27] Do not sanity check order in the fast path Mel Gorman
2009-03-16 17:53 ` [PATCH 03/27] Do not check NUMA node ID when the caller knows the node is valid Mel Gorman
2009-03-16 17:53 ` [PATCH 04/27] Check only once if the zonelist is suitable for the allocation Mel Gorman
2009-03-16 17:53 ` [PATCH 05/27] Break up the allocator entry point into fast and slow paths Mel Gorman
2009-03-16 19:30   ` Christoph Lameter
2009-03-16 17:53 ` [PATCH 06/27] Move check for disabled anti-fragmentation out of fastpath Mel Gorman
2009-03-16 17:53 ` [PATCH 07/27] Check in advance if the zonelist needs additional filtering Mel Gorman
2009-03-16 17:53 ` [PATCH 08/27] Calculate the preferred zone for allocation only once Mel Gorman
2009-03-16 17:53 ` [PATCH 09/27] Calculate the migratetype " Mel Gorman
2009-03-16 17:53 ` [PATCH 10/27] Calculate the alloc_flags " Mel Gorman
2009-03-16 17:53 ` [PATCH 11/27] Calculate the cold parameter " Mel Gorman
2009-03-16 17:53 ` [PATCH 12/27] Remove a branch by assuming __GFP_HIGH == ALLOC_HIGH Mel Gorman
2009-03-16 17:53 ` [PATCH 13/27] Inline __rmqueue_smallest() Mel Gorman
2009-03-16 18:55   ` Christoph Lameter
2009-03-16 17:53 ` [PATCH 14/27] Inline buffered_rmqueue() Mel Gorman
2009-03-16 17:53 ` [PATCH 15/27] Inline __rmqueue_fallback() Mel Gorman
2009-03-16 17:53 ` [PATCH 16/27] Save text by reducing call sites of __rmqueue() Mel Gorman
2009-03-16 17:53 ` [PATCH 17/27] Do not call get_pageblock_migratetype() more than necessary Mel Gorman
2009-03-16 17:53 ` [PATCH 18/27] Do not disable interrupts in free_page_mlock() Mel Gorman
2009-03-16 18:57   ` Christoph Lameter
2009-03-16 17:53 ` [PATCH 19/27] Do not setup zonelist cache when there is only one node Mel Gorman
2009-03-16 17:53 ` [PATCH 20/27] Use a pre-calculated value for num_online_nodes() Mel Gorman
2009-03-16 17:53 ` [PATCH 21/27] Do not check for compound pages during the page allocator sanity checks Mel Gorman
2009-03-16 17:53 ` [PATCH 22/27] Use allocation flags as an index to the zone watermark Mel Gorman
2009-03-16 17:53 ` [PATCH 23/27] Update NR_FREE_PAGES only as necessary Mel Gorman
2009-03-16 17:53 ` [PATCH 24/27] Convert gfp_zone() to use a table of precalculated values Mel Gorman
2009-03-16 19:12   ` Christoph Lameter
2009-03-18 13:52     ` Mel Gorman
2009-03-18 14:15       ` Christoph Lameter
2009-03-18 15:35         ` Mel Gorman
2009-03-18 17:21           ` Christoph Lameter
2009-03-18 18:17             ` Mel Gorman
2009-03-18 19:07               ` Christoph Lameter
2009-03-18 19:46                 ` Mel Gorman
2009-03-19  0:04                   ` KAMEZAWA Hiroyuki
2009-03-19 15:05                     ` Christoph Lameter
2009-03-19 16:53                       ` Christoph Lameter
2009-03-19 18:11                         ` Mel Gorman
2009-03-19 18:15                           ` Christoph Lameter
2009-03-19 18:37                           ` Christoph Lameter
2009-03-16 17:53 ` [PATCH 25/27] Re-sort GFP flags and fix whitespace alignment for easier reading Mel Gorman
2009-03-16 17:53 ` [PATCH 26/27] Get the pageblock migratetype without disabling interrupts 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=1237226020-14057-1-git-send-email-mel@csn.ul.ie \
    --to=mel@csn.ul.ie \
    --cc=cl@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ming.m.lin@intel.com \
    --cc=npiggin@suse.de \
    --cc=penberg@cs.helsinki.fi \
    --cc=peterz@infradead.org \
    --cc=riel@redhat.com \
    --cc=yanmin_zhang@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).