linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Lee Schermerhorn <lee.schermerhorn@hp.com>
To: linux-mm@kvack.org
Cc: akpm@linux-foundation.org, ak@suse.de, eric.whitney@hp.com,
	clameter@sgi.com, mel@skynet.ie
Subject: [PATCH/RFC 0/8] Mem Policy: More Reference Counting/Fallback Fixes and Misc Cleanups
Date: Thu, 06 Dec 2007 16:20:47 -0500	[thread overview]
Message-ID: <20071206212047.6279.10881.sendpatchset@localhost> (raw)

PATCH/RFC 00/08 Mem Policy: Reference Counting/Fallback Fixes and
		Miscellaneous mempolicy cleanup

Against: 2.6.24-rc2-mm1

  Note:  These patches are based atop Mel Gorman's "twozonelist"
  series.  Patch 5 depends on the elimination of the external
  zonelist attached to MPOL_BIND policies.  Patch 8 updates the
  mempolicy documentation to reflect a change introduced by Mel's
  patches.  I will rebase and repost less the 'RFC' and to resolve
  any comments after Mel's patches go into -mm.

Patch 1 takes mmap_sem for write when installing task memory policy.
Suggested by and originally posted by Christoph Lameter.

Patch 2 fixes a problem with fallback when a get_policy() vm_op returns
NULL.  Currently does not follow vma->task->system default policy path.

Patch 3 marks shared policies as such.  Only shared policies require 
unref after lookup.

Patch 4 just documents the mempolicy reference semantics assumed by this
series for the set and get policy vm_ops where the prototypes are defined.

Patch 5 contains the actual rework of mempolicy reference counting.  This
patch backs out the code that performed unref on all mempolicy other that
current task's and system default, and performs unref only when needed--
effectively only on shared policies.  Also updates the numa_memory_policy.txt
document to describe the memory policy reference counting semantics as I
currently understand them.

Patches 6 and 7 are cleanups of the internal usage of MPOL_DEFAULT and
MPOL_PREFERRED.

Patch 8 updates the memory policy documentation to reflect the fact that,
with Mel's twozonelist series, MPOL_BIND now searches the allowed nodes
in distance order.

This series in currently an RFC.  The patches in in this series build, boot
and survive memtoy testing on an x86_64 numa platform.  I have also tested with
instrumentation to track and report the reference counts.  So far, my testing
shows that the patches are working as I expect.

Lee Schermerhorn

--
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-12-06 21:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-06 21:20 Lee Schermerhorn [this message]
2007-12-06 21:20 ` [PATCH/RFC 1/8] Mem Policy: Write lock mmap_sem while changing task mempolicy Lee Schermerhorn
2007-12-06 21:24   ` Andi Kleen
2007-12-06 21:34     ` Lee Schermerhorn
2007-12-06 21:20 ` [PATCH/RFC 2/8] Mem Policy: Fixup Fallback for Default Shmem Policy Lee Schermerhorn
2007-12-06 21:21 ` [PATCH/RFC 3/8] Mem Policy: Mark shared policies for unref Lee Schermerhorn
2007-12-06 21:21 ` [PATCH/RFC 4/8] Mem Policy: Document {set|get}_policy() vm_ops APIs Lee Schermerhorn
2007-12-06 21:21 ` [PATCH/RFC 5/8] Mem Policy: Rework mempolicy Reference Counting [yet again] Lee Schermerhorn
2007-12-06 21:21 ` [PATCH/RFC 6/8] Mem Policy: Use MPOL_PREFERRED for system-wide default policy Lee Schermerhorn
2007-12-06 21:21 ` [PATCH/RFC 7/8] Mem Policy: MPOL_PREFERRED cleanups for "local allocation" Lee Schermerhorn
2007-12-06 21:21 ` [PATCH/RFC 8/8] Mem Policy: Fix up MPOL_BIND documentation Lee Schermerhorn

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=20071206212047.6279.10881.sendpatchset@localhost \
    --to=lee.schermerhorn@hp.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=eric.whitney@hp.com \
    --cc=linux-mm@kvack.org \
    --cc=mel@skynet.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;
as well as URLs for NNTP newsgroup(s).