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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 24 Jul 2014 10:59:51 -0700 From: Dave Hansen <dave.hansen@...el.com> To: Zhang Zhen <zhenzhang.zhang@...wei.com>, mingo@...hat.com, Yinghai Lu <yinghai@...nel.org>, mgorman@...e.de, akpm@...ux-foundation.org, zhangyanfei@...fujitsu.com CC: wangnan0@...wei.com, Linux MM <linux-mm@...ck.org>, linux-kernel@...r.kernel.org Subject: Re: [PATCH] memory-hotplug: add sysfs zone_index attribute On 07/24/2014 12:41 AM, Zhang Zhen wrote: > Currently memory-hotplug has two limits: > 1. If the memory block is in ZONE_NORMAL, you can change it to > ZONE_MOVABLE, but this memory block must be adjacent to ZONE_MOVABLE. > 2. If the memory block is in ZONE_MOVABLE, you can change it to > ZONE_NORMAL, but this memory block must be adjacent to ZONE_NORMAL. > > Without this patch, we don't know which zone a memory block is in. > So we don't know which memory block is adjacent to ZONE_MOVABLE or > ZONE_NORMAL. > > On the other hand, with this patch, we can easy to know newly added > memory is added as ZONE_NORMAL (for powerpc, ZONE_DMA, for x86_32, > ZONE_HIGHMEM). A section can contain more than one zone. This interface will lie about such sections, which is quite unfortunate. I'd really much rather see an interface that has a section itself enumerate to which zones it may be changed. The way you have it now, any user has to know the rules that you've laid out above. If the kernel changed those restrictions, we'd have to teach every application about the change in restrictions. -- 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