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, 5 Sep 2008 22:04:01 +0200 From: Andi Kleen <andi@...stfloor.org> To: Gary Hade <garyhade@...ibm.com> Cc: Andi Kleen <andi@...stfloor.org>, linux-mm@...ck.org, Andrew Morton <akpm@...ux-foundation.org>, Yasunori Goto <y-goto@...fujitsu.com>, Badari Pulavarty <pbadari@...ibm.com>, Mel Gorman <mel@....ul.ie>, Chris McDermott <lcm@...ibm.com>, linux-kernel@...r.kernel.org, x86@...nel.org, Ingo Molnar <mingo@...e.hu> Subject: Re: [PATCH] [RESEND] x86_64: add memory hotremove config option > The inability to offline all non-primary node memory sections > certainly needs to be addressed. The pgdat removal work that > Yasunori Goto has started will hopefully continue and help resolve > this issue. You make it sound like it's just some minor technical hurdle that needs to be addressed. But from all analysis of these issues I've seen so far it's extremly hard and all possible solutions have serious issues. So before doing some baby steps there should be at least some general idea how this thing is supposed to work in the end. > We have only just started thinking about issues related > to resources other that CPUs and memory that will need to be released > in preparation for node removal (e.g. memory and i/o resources > assigned to PCI devices on a node targeted for removal). That's the easy stuff. The hard parts are all the kernel objects that you cannot move. -Andi -- 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