Messages in this thread | | | Date | Mon, 6 Feb 2006 10:09:27 +0100 | From | Ingo Molnar <> | Subject | Re: [PATCH 1/5] cpuset memory spread basic implementation |
| |
* Paul Jackson <pj@sgi.com> 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?
Ingo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |