From: Andi Kleen <andi@firstfloor.org>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Andi Kleen <andi@firstfloor.org>, Dave Jones <davej@redhat.com>,
x86@kernel.org, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Update cacheline size on X86_GENERIC
Date: Sat, 11 Oct 2008 10:08:12 +0200 [thread overview]
Message-ID: <20081011080812.GA9880@one.firstfloor.org> (raw)
In-Reply-To: <200810111459.53306.nickpiggin@yahoo.com.au>
> I guess there is a reasonable argument to not care about P4 so
I don't think it is. Ignoring old systems would be a mistake
and the wrong signal. One of Linux's forte over the competition
was always to run reasonable on older systems too.
There are millions and millions of P4s around.
And they're not that old, they're still shipping in fact.
And the point of GENERIC was to be a reasonable default on all
systems.
If you want to optimize for a specific CPU you're always free
to compile the kernel for that. But GENERIC should be really
GENERIC.
> much in today's GENERIC kernel. If it is worth around 1% on tpc
> on a more modern architecture, that is a pretty big motivation
> to change it too...
TPC is a extreme case, it is extremly cache bound.
Besides I suspect the TPC issue could be fixed with a minimal
tweaks without breaking other systems.
-Andi
--
ak@linux.intel.com
next prev parent reply other threads:[~2008-10-11 8:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 17:14 Update cacheline size on X86_GENERIC Dave Jones
2008-10-10 3:28 ` Nick Piggin
2008-10-10 7:46 ` Andi Kleen
2008-10-10 8:45 ` Nick Piggin
2008-10-10 10:22 ` Andi Kleen
2008-10-11 3:59 ` Nick Piggin
2008-10-11 8:08 ` Andi Kleen [this message]
2008-10-11 8:29 ` Nick Piggin
2008-10-11 11:22 ` Andi Kleen
2008-10-11 11:27 ` Rafael J. Wysocki
2008-10-11 11:42 ` Nick Piggin
2008-10-11 13:11 ` Andi Kleen
2008-10-11 13:48 ` Nick Piggin
2008-10-11 14:01 ` Andi Kleen
2008-10-12 5:56 ` Nick Piggin
2008-10-10 18:26 ` H. Peter Anvin
2008-10-11 3:56 ` Nick Piggin
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=20081011080812.GA9880@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=x86@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