On Tue, 29 May 2012, Glauber Costa wrote: > I don't know about cpusets in details, but at least with NUMA, this is not an > apple-to-apple comparison. a NUMA node is not meant to contain you. A > container is, and that is why it is called a container. Cpusets contains sets of nodes. A cpusets "contains" nodes. These sets are associated with applications. > NUMA just means what is the *best* node to put my memory. > Now, if you actually say, through you syscalls "this is the node it should > live in", then you have a constraint, that to the best of my knowledge is > respected. Eith cpusets it means that memory needs to come from an assigned set of nodes. > Now isolation here, is done in the container boundary. (cgroups, to be > generic). Yes and with cpusets it is done at the cpuset boundary. Very much the same. -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
