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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <CAE9FiQXCG6gR-XL9fVudpNVEdS-3MHPObfWQ=Uf=q7pv33QBOA@mail.gmail.com>
Date:	Mon, 14 Oct 2013 13:37:20 -0700
From:	Yinghai Lu <yinghai@...nel.org>
To:	Tejun Heo <tj@...nel.org>
Cc:	Zhang Yanfei <zhangyanfei.yes@...il.com>,
	Zhang Yanfei <zhangyanfei@...fujitsu.com>,
	"H. Peter Anvin" <hpa@...or.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 Mon, Oct 14, 2013 at 1:04 PM, Tejun Heo <tj@...nel.org> wrote:
>> 6. in the long run, We should rework our NUMA booting:
>> a. boot system with boot numa nodes early only.
>> b. in later init stage or user space, init other nodes
>> RAM/CPU/PCI...in parallel.
>> that will reduce boot time for 8 sockets/32 sockets dramatically.
>>
>> We will need to parse srat table early so could avoid init memory for
>> non-boot nodes.
>
> Among the six you listed, this one sounds somewhat valid but still
> assuming huge page, what difference does it make?  We're just talking
> about page table alloc / init and ACPI init.  If you wanna speed up
> huge NUMA machine booting and chop down memory init per-NUMA, sure,
> move those pieces to later stages.  You can init the amount necessary
> during early boot and then bring up the rest later on.  I don't see
> why that'd require parsing SRAT.

The problem is how to define "amount necessary". If we can parse srat early,
then we could just map RAM for all boot nodes one time, instead of try some
small and then after SRAT table, expand it cover non-boot nodes.

To keep non-boot numa node hot-removable. we need to page table (and other
that we allocate during boot stage) on ram of non boot nodes, or their
local node ram.  (share page table always should be on boot nodes).

> In fact, I think there'll be more
> cases where you want to actively ignore NUMA mapping during early
> boot.  What if the system maps low memory to a non-boot numa node?

Then we treat that non-boot numa node as one of boot nodes, and it
could not be hot removed.

Actually that is BIOS or Firmware bug, they should set memory address
decoder correctly.

>
> Optimizing NUMA boot just requires moving the heavy lifting to
> appropriate NUMA nodes.  It doesn't require that early boot phase
> should strictly follow NUMA node boundaries.

At end of day, I like to see all numa system (ram/cpu/pci) could have
non boot nodes to be hot-removed logically. with any boot command
line.

Thanks

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