linux-kernel - Re: [PATCH 3/3] x86/apic: Use smaller array for __apicid_to

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: <alpine.DEB.2.11.1510121224160.6097@nanos>
Date:	Mon, 12 Oct 2015 12:25:58 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Daniel J Blueman <daniel@...ascale.com>
cc:	Jiang Liu <jiang.liu@...ux.intel.com>,
	Denys Vlasenko <dvlasenk@...hat.com>,
	Ingo Molnar <mingo@...nel.org>,
	Len Brown <len.brown@...el.com>, x86@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/3] x86/apic: Use smaller array for __apicid_to_node[]
 mapping

On Mon, 12 Oct 2015, Daniel J Blueman wrote:
> Another approach which may be suitable without changing SRAT parsing to be
> after the memory allocator is up, is to exploit the associativity of the
> bottom APIC ID bits.

What's the problem with moving (SRAT/ACPI/whatever) APIC parsing after
the memory allocator is up and available?

Thanks,

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