From: Randy Dunlap <randy.dunlap@oracle.com>
To: Lee Schermerhorn <lee.schermerhorn@hp.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-numa@vger.kernel.org, eric.whitney@hp.com
Subject: Re: [PATCH 8/15] Mempolicy: Rework mempolicy Reference Counting [yet again]
Date: Mon, 14 Apr 2008 10:32:31 -0700 [thread overview]
Message-ID: <20080414103231.60cf6005.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20080404150034.5442.92020.sendpatchset@localhost>
On Fri, 04 Apr 2008 11:00:34 -0400 Lee Schermerhorn wrote:
> PATCH 08/15 Mem Policy: rework mempolicy reference counting [yet again]
>
> Against: 2.6.25-rc8-mm1
>
> Documentation/vm/numa_memory_policy.txt | 68 ++++++++++++++
>
> Index: linux-2.6.25-rc8-mm1/Documentation/vm/numa_memory_policy.txt
> ===================================================================
> --- linux-2.6.25-rc8-mm1.orig/Documentation/vm/numa_memory_policy.txt 2008-04-02 17:47:15.000000000 -0400
> +++ linux-2.6.25-rc8-mm1/Documentation/vm/numa_memory_policy.txt 2008-04-02 17:47:26.000000000 -0400
> @@ -311,6 +311,74 @@ Components of Memory Policies
> MPOL_PREFERRED policies that were created with an empty nodemask
> (local allocation).
...
> + Because of this extra reference counting, and because we must lookup
> + shared policies in a tree structure under spinlock, shared policies are
> + more expensive to use in the page allocation path. This is expecially
especially
> + true for shared policies on shared memory regions shared by tasks running
> + on different NUMA nodes. This extra overhead can be avoided by always
> + falling back to task or system default policy for shared memory regions,
> + or by prefaulting the entire shared memory region into memory and locking
> + it down. However, this might not be appropriate for all applications.
> +
> MEMORY POLICY APIs
>
> Linux supports 3 system calls for controlling memory policy. These APIS
---
~Randy
--
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>
prev parent reply other threads:[~2008-04-14 17:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080404145944.5442.2684.sendpatchset@localhost>
[not found] ` <20080404150040.5442.49132.sendpatchset@localhost>
2008-04-14 17:23 ` [PATCH 9/15] Mempolicy: Use MPOL_PREFERRED for system-wide default policy Randy Dunlap
2008-04-14 20:05 ` Lee Schermerhorn
[not found] ` <20080404150034.5442.92020.sendpatchset@localhost>
2008-04-14 17:32 ` Randy Dunlap [this message]
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=20080414103231.60cf6005.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=eric.whitney@hp.com \
--cc=lee.schermerhorn@hp.com \
--cc=linux-mm@kvack.org \
--cc=linux-numa@vger.kernel.org \
/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).