lkml.org 
[lkml]   [2009]   [Mar]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [patch -mm] cpusets: add memory_slab_hardwall flag
On Mon, 9 Mar 2009, KOSAKI Motohiro wrote:

> My question mean, Why anyone need isolation?
> your patch insert new branch into hotpath.
> then, it makes slower hotpath a abit although a user don't use this feature.
>

On large NUMA machines, it is currently possible for a very large
percentage (if not all) of your slab allocations to come from memory that
is distant from your application's set of allowable cpus. Such
allocations that are long-lived would benefit from having affinity to
those processors. Again, this is the typical use case for cpusets: to
bind memory nodes to groups of cpus with affinity to it for the tasks
attached to the cpuset.

> typically, slab cache don't need strict node binding because
> inode/dentry touched from multiple cpus.
>

This change would obviously require inode and dentry objects to originate
from a node on the cpuset's set of mems_allowed. That would incur a
performance penalty if the cpu slab is not from such a node, but that is
assumed by the user who has enabled the option.

> In addition, on large numa systems, slab cache is relatively small
> than page cache. then this feature's improvement seems relatively small too.
>

That's irrelevant, large NUMA machines may still require memory affinity
to a specific group of cpus, the size of the global slab cache isn't
important if that's the goal. When the option is enabled for cpusets
that require that memory locality, we happily trade off partial list
fragmentation and increased slab allocations for the long-lived local
allocations.


\
 
 \ /
  Last update: 2009-03-09 21:31    [W:0.059 / U:13.908 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site