linux-kernel - Re: [PATCH part2 v2 0/8] Arrange hotpluggable memory as ZONE

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

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <525C58D3.1060705@zytor.com>
Date:	Mon, 14 Oct 2013 13:49:23 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Yinghai Lu <yinghai@...nel.org>
CC:	Zhang Yanfei <zhangyanfei.yes@...il.com>,
	Tejun Heo <tj@...nel.org>,
	Zhang Yanfei <zhangyanfei@...fujitsu.com>,
	Toshi Kani <toshi.kani@...com>, Ingo Molnar <mingo@...hat.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH part2 v2 0/8] Arrange hotpluggable memory as ZONE_MOVABLE

On 10/14/2013 01:42 PM, Yinghai Lu wrote:
>>
>> However, I don't understand how we can avoid #2, given that it is
>> fundamentally a sysadmin-driven tradeoff between performance and
>> reliability.
> 
> If we make all numa systems support nodes hot-remove logically.
> like we boot system with node0, and hot add other nodes one by one,
> we should hot remove them later.
> 

No, it doesn't work that way for memory.  You can't do nonmovable
allocations from a node that you may need to yank, unless you can
migrate that memory node transparently (which hardware can do.)

	-hpa


--
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/