From: "Mikael Pettersson" <mikpe@csd.uu.se>
To: <Administrator@smtp.paston.co.uk>
Cc: <akpm@osdl.org>, <linux-kernel@vger.kernel.org>
Subject: Re: Pentium M config option for 2.6
Date: Mon, 29 Mar 2004 16:42:27 +0100 [thread overview]
Message-ID: <01ca01c415a4$70159920$d100000a@sbs2003.local> (raw)
On Sun, 4 Jan 2004 03:28:48 +0100, Tomas Szepe wrote:
>Since the Pentium M has 64 byte cache lines and is not a K7 or K8... ;)
...
>--- a/arch/i386/Makefile 2003-09-28 11:38:05.000000000 +0200
>+++ b/arch/i386/Makefile 2004-01-04 03:02:52.000000000 +0100
>@@ -35,6 +35,7 @@
> cflags-$(CONFIG_MPENTIUMII) += $(call check_gcc,-march=pentium2,-march=i686)
> cflags-$(CONFIG_MPENTIUMIII) += $(call check_gcc,-march=pentium3,-march=i686)
> cflags-$(CONFIG_MPENTIUM4) += $(call check_gcc,-march=pentium4,-march=i686)
>+cflags-$(CONFIG_MPENTIUMM) += $(call check_gcc,-march=pentium4,-march=i686)
> cflags-$(CONFIG_MK6) += $(call check_gcc,-march=k6,-march=i586)
> # Please note, that patches that add -march=athlon-xp and friends are pointless.
> # They make zero difference whatsosever to performance at this time.
P-M is not a P4 core, it's an enhanced PIII core.
SSE2 was added, but compiler support for SSE2 f.p.
math shouldn't matter for the kernel.
Using P4 optimisations on a P-M may actually reduce
performance, due to the different micro-architectures.
(P4 made shifts and some leas more expensive, and
simple add/and/sub/etc less expensive.)
IOW, don't lie to the compiler and pretend P-M == P4
with that -march=pentium4.
And since P-M doesn't do SMP, does cache line size even
matter? There are no locks to protect from ping-ponging.
/Mikael
next reply other threads:[~2004-03-29 15:42 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-29 15:42 Mikael Pettersson [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-29 15:42 Mikael Pettersson
2004-01-05 15:09 Amit Gurdasani
2004-01-05 15:22 ` Tim Schmielau
2004-01-04 14:10 Mikael Pettersson
2004-01-04 14:43 ` Tomas Szepe
2004-01-04 15:59 ` Ciaran McCreesh
2004-03-29 15:42 ` Ciaran McCreesh
2004-03-29 15:42 ` Tomas Szepe
2004-01-04 12:27 Mikael Pettersson
2004-01-04 12:33 ` Tomas Szepe
2004-01-06 6:07 ` Jakob Oestergaard
2004-03-29 15:46 ` Jakob Oestergaard
2004-01-04 15:03 ` Rob Love
2004-01-04 16:25 ` Dave Jones
2004-01-04 16:33 ` Rob Love
2004-01-04 16:50 ` Dave Jones
2004-01-04 17:01 ` Rob Love
2004-01-04 17:14 ` Tomas Szepe
2004-03-29 15:42 ` Tomas Szepe
2004-01-04 17:03 ` Troels Walsted Hansen
2004-01-04 17:35 ` Dave Jones
2004-01-04 21:51 ` Vojtech Pavlik
2004-03-29 15:42 ` Rob Love
2004-01-04 20:34 ` Valdis.Kletnieks
2004-01-04 21:55 ` Vojtech Pavlik
2004-01-04 23:37 ` Valdis.Kletnieks
2004-03-29 15:42 ` Dave Jones
2004-03-29 15:42 ` Rob Love
2004-03-29 15:42 ` Dave Jones
2004-03-29 15:42 ` Tomas Szepe
2004-03-29 15:42 ` Rob Love
2004-01-04 2:28 Tomas Szepe
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='01ca01c415a4$70159920$d100000a@sbs2003.local' \
--to=mikpe@csd.uu.se \
--cc=Administrator@smtp.paston.co.uk \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome