| 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.0802041101290.9656@schroedinger.engr.sgi.com> Date: Mon, 4 Feb 2008 11:03:32 -0800 (PST) From: Christoph Lameter <clameter@....com> To: Andi Kleen <andi@...stfloor.org> cc: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>, linux-mm@...ck.org, linux-kernel@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org>, Lee.Schermerhorn@...com Subject: Re: [2.6.24-rc8-mm1][regression?] numactl --interleave=all doesn't works on memoryless node. On Sat, 2 Feb 2008, Andi Kleen wrote: > To be honest I've never tried seriously to make 32bit NUMA policy > (with highmem) work well; just kept it at a "should not break" > level. That is because with highmem the kernel's choices at > placing memory are seriously limited anyways so I doubt 32bit > NUMA will ever work very well. Memory policies do not work reliably with config highmem (I have never seen such usage because large memory systems are typically 64 bit which have no highmem, but there are some 32bit numa uses of HIGHMEM) .... Memory policies are only applied to the highest zone. So if a system has highmem on some nodes and not on the others then policies will only be applied if allocations happen to occur on the highmem nodes. -- 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