From: "H. Peter Anvin" <hpa@zytor.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Zhang Yanfei <zhangyanfei.yes@gmail.com>,
Tejun Heo <tj@kernel.org>,
Zhang Yanfei <zhangyanfei@cn.fujitsu.com>,
Toshi Kani <toshi.kani@hp.com>, Ingo Molnar <mingo@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH part2 v2 0/8] Arrange hotpluggable memory as ZONE_MOVABLE
Date: Mon, 14 Oct 2013 13:49:23 -0700 [thread overview]
Message-ID: <525C58D3.1060705@zytor.com> (raw)
In-Reply-To: <CAE9FiQUQaB2RAPyNjW8vF1uEigCEaxVFH1PBs=xgYNRRCpZPuw@mail.gmail.com>
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
prev parent reply other threads:[~2013-10-14 20:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-12 6:00 [PATCH part2 v2 0/8] Arrange hotpluggable memory as ZONE_MOVABLE Zhang Yanfei
2013-10-12 6:03 ` [PATCH part2 v2 1/8] x86: get pg_data_t's memory from other node Zhang Yanfei
2013-10-12 6:04 ` [PATCH part2 v2 2/8] memblock, numa: Introduce flag into memblock Zhang Yanfei
2013-10-12 6:05 ` [PATCH part2 v2 3/8] memblock, mem_hotplug: Introduce MEMBLOCK_HOTPLUG flag to mark hotpluggable regions Zhang Yanfei
2013-10-12 6:06 ` [PATCH part2 v2 4/8] memblock: Make memblock_set_node() support different memblock_type Zhang Yanfei
2013-10-12 6:07 ` [PATCH part2 v2 5/8] acpi, numa, mem_hotplug: Mark hotpluggable memory in memblock Zhang Yanfei
2013-10-12 6:08 ` [PATCH part2 v2 6/8] acpi, numa, mem_hotplug: Mark all nodes the kernel resides un-hotpluggable Zhang Yanfei
2013-10-12 6:09 ` [PATCH part2 v2 7/8] memblock, mem_hotplug: Make memblock skip hotpluggable regions if needed Zhang Yanfei
2013-10-12 6:09 ` [PATCH part2 v2 8/8] x86, numa, acpi, memory-hotplug: Make movable_node have higher priority Zhang Yanfei
[not found] ` <525B19C3.9040907@gmail.com>
[not found] ` <20131014133835.GG4722@htj.dyndns.org>
[not found] ` <525BFCF3.5010908@gmail.com>
[not found] ` <20131014142719.GI4722@htj.dyndns.org>
[not found] ` <525C02DC.4050706@gmail.com>
[not found] ` <20131014145131.GJ4722@htj.dyndns.org>
[not found] ` <525C0866.2010808@gmail.com>
[not found] ` <20131014151902.GL4722@htj.dyndns.org>
2013-10-14 15:34 ` [PATCH part2 v2 0/8] Arrange hotpluggable memory as ZONE_MOVABLE Zhang Yanfei
2013-10-14 19:34 ` Yinghai Lu
2013-10-14 20:04 ` Tejun Heo
2013-10-14 20:37 ` Yinghai Lu
2013-10-14 20:42 ` H. Peter Anvin
2013-10-15 6:50 ` Ingo Molnar
2013-10-15 17:31 ` H. Peter Anvin
2013-10-16 7:03 ` Ingo Molnar
2013-10-14 20:55 ` Tejun Heo
2013-10-15 1:40 ` Zhang Yanfei
2013-10-15 2:25 ` Yinghai Lu
2013-10-15 13:16 ` Tejun Heo
2013-10-14 20:35 ` H. Peter Anvin
2013-10-14 20:42 ` Yinghai Lu
2013-10-14 20:49 ` H. Peter Anvin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=525C58D3.1060705@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tj@kernel.org \
--cc=toshi.kani@hp.com \
--cc=yinghai@kernel.org \
--cc=zhangyanfei.yes@gmail.com \
--cc=zhangyanfei@cn.fujitsu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox