From: Thomas Horsten <thomas@horsten.com>
To: Dave Jones <davej@suse.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
"H . Peter Anvin" <hpa@zytor.com>,
Michael Elizabeth Chastain <mec@shout.net>
Subject: Re: [PATCH] 2.5.69 Changes to Kconfig and i386 Makefile to include support for various K7 optimizations
Date: Wed, 14 May 2003 19:40:10 +0100 [thread overview]
Message-ID: <200305141940.10999.thomas@horsten.com> (raw)
In-Reply-To: <20030514160449.B28115@suse.de>
On Wednesday 14 May 2003 15:04, Dave Jones wrote:
> > I made this patch to support the various K7 model-specific
> > optimizations that the later GCC compilers can use.
> >
> > Please have a look, and pass me any comments.
>
> I don't think this is worth the extra complication. The potential wins
> (if any) outweigh the confusion to users who might have no clue as to
> what core they have. Additionally, some gcc's got these options wrong.
> The athlon4 option was completely wrong for a while for eg.
I think when GCC supports the different cores, it should be supported by the
kernel scripts, the differences between the cores are real enough to have
potential optimizations at least in theory (as far as I could see the only
difference in GCC 3.2 is whether to use SSE, but that could change in the
future).
Maybe it should be renamed "Advanced CPU model selection", or something like
that, instead of "K7 Model Selection", but the help IMHO makes it clear
enough that you should go with the default if you are not sure and that it
will work on any core.
I think it's a fairly simple patch that doesn't break anything, and there are
certainly options lurking around in Kconfig that are much more obscure than
this :)
> > I also have the same patch for 2.4, if you are interested it's
> > available on my Linux page on http://www.infowares.com/linux
>
> For 2.4, it's an even worse idea IMO.
I completely agree that this shouldn't go into the stock 2.4 kernel, that's
also why I didn't post it here. It's just on my site as a convenience for
those who might want to use the XP specific options etc. in an easy way (like
I use it myself).
// Thomas
next prev parent reply other threads:[~2003-05-14 18:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200305071834.26789.thomas@horsten.com>
2003-05-14 14:04 ` [PATCH] 2.5.69 Changes to Kconfig and i386 Makefile to include support for various K7 optimizations Dave Jones
2003-05-14 18:40 ` Thomas Horsten [this message]
2003-05-14 18:55 ` Dave Jones
2003-05-14 16:49 Ray Lee
2003-05-14 17:06 ` Dave Jones
-- strict thread matches above, loose matches on Subject: below --
2003-05-07 19:28 Thomas Horsten
2003-05-07 20:06 ` Ken Witherow
2003-05-07 20:44 ` Thomas Horsten
2003-05-07 21:02 ` Thomas Horsten
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=200305141940.10999.thomas@horsten.com \
--to=thomas@horsten.com \
--cc=davej@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mec@shout.net \
/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