From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Andi Kleen <andi@firstfloor.org>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
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 13:27:26 +0200 [thread overview]
Message-ID: <200810111327.27121.rjw@sisk.pl> (raw)
In-Reply-To: <20081011112218.GA12131@one.firstfloor.org>
On Saturday, 11 of October 2008, Andi Kleen wrote:
> On Sat, Oct 11, 2008 at 07:29:19PM +1100, Nick Piggin wrote:
> > I also think there are reasonable arguments the other way, and I
> > personally also think it might be better to leave it 128 (even
> > if it is unlikely, introducing a regression is not good).
>
> The issue is also that the regression will be likely large.
> False sharing can really hurt when it hits as you know, because
> the penalties are so large.
>
> > > There are millions and millions of P4s around.
> > > And they're not that old, they're still shipping in fact.
> >
> > Still shipping in anything aside from 1s systems?
>
> Remember the first Core2 based 4S (Tigerton) Xeon was only introduced last year
> and that market is quite conservative. For 2S it's a bit longer, but
> it wouldn't surprise me there if new systems are still shipping.
>
> Also to be honest I doubt the theory that older systems
> are never upgraded to newer OS.
Actaually, I have examples to the contrary. :-)
Thanks,
Rafael
next prev parent reply other threads:[~2008-10-11 11:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 17:14 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
2008-10-11 8:29 ` Nick Piggin
2008-10-11 11:22 ` Andi Kleen
2008-10-11 11:27 ` Rafael J. Wysocki [this message]
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=200810111327.27121.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=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
all inboxes | Powered by JetHome®