linux-kernel - Re: Choosing a HyperThreading/SMP/MultiCore kernel ?

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: <45A8CB9F.3020506@s5r6.in-berlin.de>
Date:	Sat, 13 Jan 2007 13:07:59 +0100
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Valdis.Kletnieks@...edu
CC:	Lennart Sorensen <lsorense@...lub.uwaterloo.ca>,
	Sunil Naidu <akula2.shark@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: Choosing a HyperThreading/SMP/MultiCore kernel ?

On 1/13/2007 4:38 AM, Valdis.Kletnieks@...edu wrote:
> On Fri, 12 Jan 2007 10:03:49 EST, Lennart Sorensen said:
>> I believe the closest optimization for a Core2 is probably the Pentium M
>> (certainly not the P4/netburst).  Not entirely sure though.
> 
> CONFIG_MCORE2=y
> 
> That's probably even closer :)  At least in 2.6.20-rc4-mm1.  

Here is some more information, not about kernel configuration parameters
but more generally about gcc flags to be used with Core and Core 2 CPUs:
http://www.gentoo.org/news/en/gwn/20061211-newsletter.xml#doc_chap2_sect3

Quoting their source, http://psykil.livejournal.com/2006/12/03/:
| If you're using GCC 4.1, use -march=prescott for Intel Core Solo/Duo
| and -march=nocona (and an amd64 profile) for Core 2 Solo/Duo.  For GCC
| 4.2, a Core Solo/Duo should use -march=prescott -mtune=generic, and
| Core 2 Solo/Duo should be set to -march=nocona -mtune=generic.  GCC
| trunk adds -march=core2 and support for the SSSE3 instruction set, but
| that won't be out for quite a while yet.
|
| If you do happen to be using GCC 4.2, check out the very cool
| -march=native, which will autodetect the host processor(s) and set
| -march and -mtune accordingly. For Core CPU's you'll also need the
| patch from GCC PR #30040.

-- 
Stefan Richter
-=====-=-=== ---= -==-=
http://arcgraph.de/sr/
-
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/