mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Andi Kleen <andi@firstfloor.org>,
	Phil Endecott <phil_wueww_endecott@chezphil.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Mention Intel Atom in Kconfig.cpu
Date: Mon, 13 Oct 2008 17:02:30 +0300	[thread overview]
Message-ID: <20081013140228.GG29938@cs181140183.pp.htv.fi> (raw)
In-Reply-To: <20081013093014.607c5925@infradead.org>

On Mon, Oct 13, 2008 at 09:30:14AM -0400, Arjan van de Ven wrote:
> On Mon, 13 Oct 2008 15:30:51 +0200
> Andi Kleen <andi@firstfloor.org> wrote:
> > 
> > > Core2 instruction set with tune=generic is still the best to set.
> > 
> > Not sure that is true. These option are mostly for the compiler.
> 
> exactly, and our benchmarks show that tune=generic is best right now
> for Atom. 
> (586 scheduling sounds nice, but the pipelines are rather different.
> And the benchmarks don't lie..  ;-)

That sounds a bit dangerous since tune=generic is documented to change 
the semantics between gcc versions to better fit more recent CPUs
(there's even a small difference between gcc 4.2 and gcc 4.3):

          As new processors are deployed in the marketplace, the
          behavior of this option will change.  Therefore, if you
          upgrade to a newer version of GCC, the code generated option
          will change to reflect the processors that were most common
          when that version of GCC was released.


cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  parent reply	other threads:[~2008-10-13 14:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-13 10:58 Phil Endecott
2008-10-13 12:13 ` [PATCH] Mention Intel Atom in Kconfig.cpu (less garbled this time) Phil Endecott
2008-10-13 15:36   ` J.A. Magallón
2008-10-13 12:28 ` [PATCH] Mention Intel Atom in Kconfig.cpu Andi Kleen
2008-10-13 13:18   ` Arjan van de Ven
2008-10-13 13:30     ` Andi Kleen
2008-10-13 13:30       ` Arjan van de Ven
2008-10-13 13:53         ` Andi Kleen
2008-10-13 14:02         ` Adrian Bunk [this message]
2008-10-13 14:17           ` Arjan van de Ven
2008-10-13 19:22             ` Phil Endecott

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=20081013140228.GG29938@cs181140183.pp.htv.fi \
    --to=bunk@kernel.org \
    --cc=andi@firstfloor.org \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phil_wueww_endecott@chezphil.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®