linux-kernel - Re: x86: Convert cpu_core_map to be a per cpu variable

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] [day] [month] [year] [list]

Message-ID: <20070723123408.618ea0a3@schroedinger.engr.sgi.com>
Date:	Mon, 23 Jul 2007 12:34:08 -0700
From:	Christoph Lameter <clameter@....com>
To:	"Siddha, Suresh B" <suresh.b.siddha@...el.com>
Cc:	ak@...e.de, linux-kernel@...r.kernel.org, travis@....com,
	Jeremy Fitzhardinge <jeremy@...p.org>
Subject: Re: x86: Convert cpu_core_map to be a per cpu variable

On Tue, 17 Jul 2007 12:27:18 -0700
"Siddha, Suresh B" <suresh.b.siddha@...el.com> wrote:


> Is there a reason why cpu_sibling_map[] is left out in these changes?

Yes this patch is a trial balloon to make sure that I/we do the right
thing when dealing with the other cpu maps. Patchset will hopefully
soon be forthcoming (after I have dealt with the pile of emails/issues
that came in during my vacation). I'd be glad if someone else could do
it???

Hopefully yours,
	C

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