lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <Pine.LNX.4.64.0710261038250.15270@schroedinger.engr.sgi.com> Date: Fri, 26 Oct 2007 10:39:34 -0700 (PDT) From: Christoph Lameter <clameter@....com> To: Paul Jackson <pj@....com> cc: rientjes@...gle.com, akpm@...ux-foundation.org, ak@...e.de, Lee.Schermerhorn@...com, linux-kernel@...r.kernel.org Subject: Re: [patch 3/3] cpusets: add memory_spread_user option On Fri, 26 Oct 2007, Paul Jackson wrote: > For example, if they pass in a mask with all bits sets, then they > get interleave over all the nodes in their current cpuset, even as > that cpuset changes. If they pass in a mask with say just two > bits set, then they will get interleave over just two nodes anytime > they are in a cpuset with two or more nodes (when in a single node > cpuset, they will of course get no interleave, for lack of anything > to interleave over.) Yuck. I really want cpuset relative nodemasks. Nodes need to reference to available nodes. If you set all of them then it will use all available nodes and ignore the ones not allowed. If you just set the first two bits then it will use the first and second node of a cpuset. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists