[lkml]   [2006]   [Feb]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 1/5] cpuset memory spread basic implementation

* Paul Jackson <> wrote:

> It's job specific, and cache specific.
> If the job has a number of threads hitting the same data set and:
> 1) the data set is faulted in non-uniformly (perhaps some
> job init task reads it in), and
> 2) the data set is accessed with little thread locality
> (one thread is as likely as the next to read or write
> a particular page),
> then for that job spreading makes sense.
> If the cache is one that goes with a data set, such as file system
> buffers (page cache) and inode and dentry slab caches, then for that
> cache spreading makes sense. (Yes Andrew, your xfs query is still in
> my queue.)
> But for many (most?) other jobs and other caches, the default
> node-local policy is better.

what type of objects need to be spread (currently)? It seems that your
current focus is on filesystem related objects: pagecache, inodes,
dentries - correct? Is there anything else that needs to be spread? In
particular, does any userspace mapped memory need to be spread - or is
it handled with other mechanisms?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-02-06 10:13    [W:0.108 / U:4.108 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site