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

Message-Id: <20070713.154119.15263594.davem@davemloft.net>
Date:	Fri, 13 Jul 2007 15:41:19 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	clameter@....com
Cc:	ak@...e.de, linux-kernel@...r.kernel.org, travis@....com,
	jeremy@...p.org
Subject: Re: x86: Convert cpu_core_map to be a per cpu variable

From: Christoph Lameter <clameter@....com>
Date: Fri, 13 Jul 2007 09:34:02 -0700 (PDT)

> But the code modified here is x86_64 and i386 specific? Is there an 
> overlap?

I see, the acessor is abstracted via a function.

That seems pointless, and allows you to do things like this, improving
the implementation on one set of platforms yet leave others using
SMT/multi-core scheduling behind.

It makes a lot more sense to make the implementation consistent
and therefore the improvements are seen on every platform.
-
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/