From: Jeff Law <jeffreyalaw@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: linux-riscv@lists.infradead.org,
Palmer Dabbelt <palmer@rivosinc.com>,
Xu Lu <luxu.kernel@bytedance.com>
Subject: Re: Page sizes supported by RISC-V
Date: Sun, 29 Sep 2024 09:18:34 -0600 [thread overview]
Message-ID: <cbbc9925-12a5-4043-a6c5-ccd1ef0997c8@gmail.com> (raw)
In-Reply-To: <8734lixzss.fsf@oldenburg.str.redhat.com>
On 9/29/24 9:08 AM, Florian Weimer wrote:
>
> I understand that not making a call in the specifications avoids the
> need to resolve these conflicts. But if you don't define a maximum page
> size there, it is effectively specified as 4096 bytes. This will cause
> problems if distributions targeting large systems want a larger page
> size because it better aligns with the kind of hardware they target.
> It's really bad for cross-distribution binary compatibility, something
> that's important outside the embedded space and probably necessary for
> mainstreaming.
>
> (Of course you know all this. 8-)
Yup. Once it's baked into one significant distro, it's doing to be
bloody hard to change. I'm sure we both remember the PPC pagesize stuff
from a few years back ;(
I strongly suspect the lack of specification here is mean to give
degrees of freedom to the implementors, but sometimes those writing the
specs don't really understand the implication of leaving things like
this unspecified and how much pain it really causes in the end.
Jeff
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2024-09-29 15:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-28 16:35 Page sizes supported by RISC-V Florian Weimer
2024-09-29 3:29 ` [External] " Xu Lu
2024-09-29 5:04 ` Florian Weimer
2024-09-29 5:18 ` Xu Lu
2024-09-29 14:51 ` Jeff Law
2024-09-29 15:08 ` Florian Weimer
2024-09-29 15:18 ` Jeff Law [this message]
2024-09-29 15:49 ` Maciej W. Rozycki
2024-10-02 15:25 ` Palmer Dabbelt
2025-01-15 2:00 ` Jeff Law
2025-01-15 6:51 ` Maciej W. Rozycki
2025-01-15 7:51 ` Florian Weimer
2025-01-15 9:03 ` Maciej W. Rozycki
2025-01-15 14:58 ` Jeff Law
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=cbbc9925-12a5-4043-a6c5-ccd1ef0997c8@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=fweimer@redhat.com \
--cc=linux-riscv@lists.infradead.org \
--cc=luxu.kernel@bytedance.com \
--cc=palmer@rivosinc.com \
/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