From: "H. Peter Anvin" <hpa@kernel.org>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Dave Jones <davej@redhat.com>,
x86@kernel.org, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Update cacheline size on X86_GENERIC
Date: Fri, 10 Oct 2008 11:26:55 -0700 [thread overview]
Message-ID: <48EF9E6F.5050006@kernel.org> (raw)
In-Reply-To: <200810101428.23662.nickpiggin@yahoo.com.au>
Nick Piggin wrote:
> I think P4 technically did have 64 byte cachelines, but had some adjacent
> line prefetching. And AFAIK core2 CPUs can do similar prefetching (but
> maybe it's smarter and doesn't cause so much bouncing?).
>
> Anyway, GENERIC kernel should run well on all architectures, and while
> going too big causes slightly increased structures sometimes, going too
> small could result in horrible bouncing.
Well, GENERIC really is targetted toward the commercial mainstream at
the time, with the additional caveat that it shouldn't totally suck on
anything that isn't so obscure it's irrelevant. It is thus a moving
target. 1% on TPC doesn't count as "totally suck", especially since by
now anyone who is running workloads like TPC either will have phased out
their P4s or they don't care about performance at all.
> Lastly, I think x86 will go to 128 byte lines in the next year or two, so
> maybe at this point we can just keep 128 byte alignment?
"x86" doesn't have a cache line size; a specific implementation will.
Which particular implementation do you believe is going to 128-byte L1
cachelines?
-hpa
next prev parent reply other threads:[~2008-10-10 18:27 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
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 [this message]
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=48EF9E6F.5050006@kernel.org \
--to=hpa@kernel.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