From: Segher Boessenkool <segher@kernel.crashing.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: paulmck <paulmck@kernel.org>,
"Aneesh Kumar K.V" <aneesh.kumar@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Nicholas Piggin <npiggin@gmail.com>,
"Naveen N. Rao" <naveen.n.rao@linux.ibm.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: Appropriate liburcu cache line size for Power
Date: Tue, 26 Mar 2024 13:20:26 -0500 [thread overview]
Message-ID: <20240326182026.GE19790@gate.crashing.org> (raw)
In-Reply-To: <87ttktiho5.fsf@mail.lhotse>
On Tue, Mar 26, 2024 at 06:19:38PM +1100, Michael Ellerman wrote:
> Mathieu Desnoyers <mathieu.desnoyers@efficios.com> writes:
> The ISA doesn't specify the cache line size, other than it is smaller
> than a page.
It also says it is "aligned". Nowhere is it said what an aligned size
is, but it seems clear it has to be a power of two.
> In practice all the 64-bit IBM server CPUs I'm aware of have used 128
> bytes.
Yup. It is 128B on p3 already.
> It is possible to discover at runtime via AUXV headers. But that's no
> use if you want a compile-time constant.
The architecture does not require the data block size to be equal to the
instruction block size, already. But many programs subscribe to an
overly simplified worldview, which is a big reason everything is 128B on
all modern PowerPC.
It is quite a nice tradeoff size, there has to be a huge change in the
world for this to ever change :-)
Segher
prev parent reply other threads:[~2024-03-26 18:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-24 12:20 Appropriate liburcu cache line size for Power Mathieu Desnoyers
2024-03-25 20:34 ` Nathan Lynch
2024-03-25 21:23 ` Segher Boessenkool
2024-03-28 18:30 ` Mathieu Desnoyers
2024-03-26 7:19 ` Michael Ellerman
2024-03-26 14:37 ` Mathieu Desnoyers
2024-04-02 7:17 ` Michael Ellerman
2024-03-26 18:20 ` Segher Boessenkool [this message]
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=20240326182026.GE19790@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=aneesh.kumar@kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mpe@ellerman.id.au \
--cc=naveen.n.rao@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=paulmck@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;
as well as URLs for NNTP newsgroup(s).