| 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
| ||
|
Date: Tue, 19 Feb 2008 19:42:49 +0900 From: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com> To: kernel list <linux-kernel@...r.kernel.org>, Trivial patch monkey <trivial@...nel.org>, Paul Jackson <pj@....com>, Christoph Lameter <clameter@....com>, Paul Menage <menage@...gle.com> Cc: kosaki.motohiro@...fujitsu.com Subject: cpuset trivial documentation fix s/N_MEMORY/N_HIGH_MEMORY/ Hi, this is easy documentation fix. current implementation of cpuset track N_HIGH_MEMORY instead N_MEMORY. (N_MEMORY doesn't exist in current implementation) Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com> CC: Paul Jackson <pj@....com> CC: Christoph Lameter <clameter@....com> CC: Paul Menage <menage@...gle.com> --- Documentation/cpusets.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) Index: b/Documentation/cpusets.txt =================================================================== --- a/Documentation/cpusets.txt 2008-02-14 13:42:22.000000000 +0900 +++ b/Documentation/cpusets.txt 2008-02-19 19:37:14.000000000 +0900 @@ -209,7 +209,7 @@ and name space for cpusets, with a minim The cpus and mems files in the root (top_cpuset) cpuset are read-only. The cpus file automatically tracks the value of cpu_online_map using a CPU hotplug notifier, and the mems file -automatically tracks the value of node_states[N_MEMORY]--i.e., +automatically tracks the value of node_states[N_HIGH_MEMORY]--i.e., nodes with memory--using the cpuset_track_online_nodes() hook. -- 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