| 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: <m2d3gm0we2.fsf@firstfloor.org> Date: Wed, 03 Aug 2011 18:59:33 -0700 From: Andi Kleen <andi@...stfloor.org> To: Rafael Aquini <aquini@...hat.com> Cc: linux-mm@...ck.org, Andrew Morton <akpm@...ux-foundation.org>, KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>, Stephen Wilson <wilsons@...rt.ca>, Andrea Arcangeli <aarcange@...hat.com>, Christoph Lameter <cl@...ux.com>, Rik van Riel <riel@...hat.com>, linux-kernel@...r.kernel.org Subject: Re: [PATCH] mm/mempolicy.c: make sys_mbind & sys_set_mempolicy aware of task_struct->mems_allowed Rafael Aquini <aquini@...hat.com> writes: > Among several other features enabled when CONFIG_CPUSETS is defined, > task_struct is enhanced with the nodemask_t mems_allowed element that > serves to register/report on which memory nodes the task may obtain > memory. Also, two new lines that reflect the value registered at > task_struct->mems_allowed are added to the '/proc/[pid]/status' file: As Christoph said this was intentionally designed this way. Originally there was some consideration of "relative policies", but that is not implemented and had various issues. They're orthogonal mechanisms. -Andi -- ak@...ux.intel.com -- Speaking for myself only -- 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