* Re: [PATCH 9/15] Mempolicy: Use MPOL_PREFERRED for system-wide default policy
[not found] ` <20080404150040.5442.49132.sendpatchset@localhost>
@ 2008-04-14 17:23 ` Randy Dunlap
2008-04-14 20:05 ` Lee Schermerhorn
0 siblings, 1 reply; 3+ messages in thread
From: Randy Dunlap @ 2008-04-14 17:23 UTC (permalink / raw)
To: Lee Schermerhorn; +Cc: akpm, linux-mm, linux-numa, eric.whitney
On Fri, 04 Apr 2008 11:00:40 -0400 Lee Schermerhorn wrote:
> PATCH 09/15 Mempolicy: Use MPOL_PREFERRED for system-wide default policy
>
> Against: 2.6.25-rc8-mm1
>
> Signed-off-by: Lee Schermerhorn <lee.schermerhorn@hp.com>
>
> Documentation/vm/numa_memory_policy.txt | 52 ++++++++----------------
> mm/mempolicy.c | 68 +++++++++++++++++++-------------
> 2 files changed, 59 insertions(+), 61 deletions(-)
>
> 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:26.000000000 -0400
> +++ linux-2.6.25-rc8-mm1/Documentation/vm/numa_memory_policy.txt 2008-04-02 17:47:37.000000000 -0400
> @@ -187,19 +170,18 @@ Components of Memory Policies
>
> MPOL_PREFERRED: This mode specifies that the allocation should be
> attempted from the single node specified in the policy. If that
> - allocation fails, the kernel will search other nodes, exactly as
> - it would for a local allocation that started at the preferred node
> - in increasing distance from the preferred node. "Local" allocation
> - policy can be viewed as a Preferred policy that starts at the node
> + allocation fails, the kernel will search other nodes, in order of
> + increasing distance from the preferred node based on information
> + provided by the platform firmware.
> containing the cpu where the allocation takes place.
Something in the patch lines above seems to be foobarred.
I.e., the sentences/lines don't flow correctly.
> Internally, the Preferred policy uses a single node--the
---
~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>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH 8/15] Mempolicy: Rework mempolicy Reference Counting [yet again]
[not found] ` <20080404150034.5442.92020.sendpatchset@localhost>
@ 2008-04-14 17:32 ` Randy Dunlap
0 siblings, 0 replies; 3+ messages in thread
From: Randy Dunlap @ 2008-04-14 17:32 UTC (permalink / raw)
To: Lee Schermerhorn; +Cc: akpm, linux-mm, linux-numa, eric.whitney
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>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH 9/15] Mempolicy: Use MPOL_PREFERRED for system-wide default policy
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
0 siblings, 0 replies; 3+ messages in thread
From: Lee Schermerhorn @ 2008-04-14 20:05 UTC (permalink / raw)
To: Randy Dunlap; +Cc: akpm, linux-mm, linux-numa, eric.whitney
On Mon, 2008-04-14 at 10:23 -0700, Randy Dunlap wrote:
> On Fri, 04 Apr 2008 11:00:40 -0400 Lee Schermerhorn wrote:
>
> > PATCH 09/15 Mempolicy: Use MPOL_PREFERRED for system-wide default policy
> >
> > Against: 2.6.25-rc8-mm1
> >
> > Signed-off-by: Lee Schermerhorn <lee.schermerhorn@hp.com>
> >
> > Documentation/vm/numa_memory_policy.txt | 52 ++++++++----------------
> > mm/mempolicy.c | 68 +++++++++++++++++++-------------
> > 2 files changed, 59 insertions(+), 61 deletions(-)
> >
> > 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:26.000000000 -0400
> > +++ linux-2.6.25-rc8-mm1/Documentation/vm/numa_memory_policy.txt 2008-04-02 17:47:37.000000000 -0400
>
> > @@ -187,19 +170,18 @@ Components of Memory Policies
> >
> > MPOL_PREFERRED: This mode specifies that the allocation should be
> > attempted from the single node specified in the policy. If that
> > - allocation fails, the kernel will search other nodes, exactly as
> > - it would for a local allocation that started at the preferred node
> > - in increasing distance from the preferred node. "Local" allocation
> > - policy can be viewed as a Preferred policy that starts at the node
> > + allocation fails, the kernel will search other nodes, in order of
> > + increasing distance from the preferred node based on information
> > + provided by the platform firmware.
> > containing the cpu where the allocation takes place.
>
> Something in the patch lines above seems to be foobarred.
> I.e., the sentences/lines don't flow correctly.
Looks like I forgot to delete the line starting with 'containing ...'.
I'll fix it, along with the 'expecially' in patch 8. [That's not a word,
huh? :)]
Lee
--
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>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2008-04-14 20:05 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[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 ` [PATCH 8/15] Mempolicy: Rework mempolicy Reference Counting [yet again] Randy Dunlap
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).