LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Valdis.Kletnieks@vt.edu
Cc: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
	Sunil Naidu <akula2.shark@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Choosing a HyperThreading/SMP/MultiCore kernel ?
Date: Sat, 13 Jan 2007 13:07:59 +0100	[thread overview]
Message-ID: <45A8CB9F.3020506@s5r6.in-berlin.de> (raw)
In-Reply-To: <200701130338.l0D3chOs026407@turing-police.cc.vt.edu>

On 1/13/2007 4:38 AM, Valdis.Kletnieks@vt.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/

  reply	other threads:[~2007-01-13 12:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-12 13:25 Sunil Naidu
2007-01-12 15:03 ` Lennart Sorensen
2007-01-12 23:21   ` Sunil Naidu
2007-01-12 23:29     ` Paul Jackson
2007-01-13  3:38   ` Valdis.Kletnieks
2007-01-13 12:07     ` Stefan Richter [this message]
2007-01-13 17:54     ` Lennart Sorensen
2007-01-14  2:21       ` Valdis.Kletnieks
2007-01-20  3:45       ` Sunil Naidu
2007-01-13 20:18     ` Bill Davidsen
2007-01-14  1:55       ` Valdis.Kletnieks
2007-01-14 15:52         ` Bill Davidsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45A8CB9F.3020506@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akula2.shark@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lsorense@csclub.uwaterloo.ca \
    --subject='Re: Choosing a HyperThreading/SMP/MultiCore kernel ?' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).