| 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: Fri, 11 Jul 2014 13:20:51 -0700 From: Andi Kleen <andi@...stfloor.org> To: Greg KH <gregkh@...uxfoundation.org> Cc: Jiang Liu <jiang.liu@...ux.intel.com>, Peter Zijlstra <peterz@...radead.org>, Andrew Morton <akpm@...ux-foundation.org>, Mel Gorman <mgorman@...e.de>, David Rientjes <rientjes@...gle.com>, Mike Galbraith <umgwanakikbuti@...il.com>, "Rafael J . Wysocki" <rafael.j.wysocki@...el.com>, Tony Luck <tony.luck@...el.com>, linux-mm@...ck.org, linux-hotplug@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [RFC Patch V1 00/30] Enable memoryless node on x86 platforms Greg KH <gregkh@...uxfoundation.org> writes: > On Fri, Jul 11, 2014 at 10:29:56AM +0200, Peter Zijlstra wrote: >> On Fri, Jul 11, 2014 at 03:37:17PM +0800, Jiang Liu wrote: >> > Any comments are welcomed! >> >> Why would anybody _ever_ have a memoryless node? That's ridiculous. > > I'm with Peter here, why would this be a situation that we should even > support? Are there machines out there shipping like this? We've always had memory nodes. A classic case in the old days was a two socket system where someone didn't populate any DIMMs on the second socket. There are other cases too. -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