Messages in this thread | | | Date | Mon, 6 Feb 2006 01:27:26 -0800 | From | Paul Jackson <> | Subject | Re: [PATCH 1/5] cpuset memory spread basic implementation |
| |
Ingo asked: > what type of objects need to be spread (currently)? It seems that your > current focus is on filesystem related objects:
In addition to the filesystem related objects called out in this current patch set, we also have some xfs directory and inode caches. An xfs patch is winding its way toward lkml that will enhance the xfs cache creation calls a little, so that we can pick off the particular slab caches we need to be able to spread, while leaving other xfs slab caches with the default node-local policy.
> does any userspace mapped memory need to be spread
I don't think so, but I am not entirely confident of my answer tonight. I would expect the applications I care about to place mapped pages by being careful to make the first access (load or store) of that page from a cpu on the node where they wanted that page placed.
So, yes, either mostly filesystem related objects, or all such.
I'm not sure which.
-- I won't rest till it's the best ... Programmer, Linux Scalability Paul Jackson <pj@sgi.com> 1.925.600.0401 - 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/
| |