linux-kernel - Re: [PATCH 0/3] x86: adapt CPU topology detection for AMD Magny-Cours

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: <87vdogbp4g.fsf@basil.nowhere.org>
Date:	Mon, 04 May 2009 22:16:15 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Andreas Herrmann <andreas.herrmann3@....com>
Cc:	Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] x86: adapt CPU topology detection for AMD Magny-Cours

Andreas Herrmann <andreas.herrmann3@....com> writes:

> Following patches add support for AMD Magny-Cours CPU.
>
> I slightly change struct cpuinfo where I'd like to introduce
> cpu_node_id to reflect CPU topology for AMD Magny-Cours CPU which
> consists of two internal-nodes.

It's unclear to me why you need this special case versus 
just using the normal NUMA distances to represent the internal
nodes as "nearby nodes" versus sockets as "farer away".

Essentially it should be just two level NUMA which can be already
described fine for the scheduler or VM using the existing SRAT
mechanism.

Who needs this additional information?

-Andi

-- 
ak@...ux.intel.com -- Speaking for myself only.
--
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/