From: Florian Weimer <fweimer@redhat.com>
To: Xu Lu <luxu.kernel@bytedance.com>
Cc: linux-riscv@lists.infradead.org,
Jeff Law <jeffreyalaw@gmail.com>,
Palmer Dabbelt <palmer@rivosinc.com>,
Punit Agrawal <punit.agrawal@bytedance.com>,
wangpengcheng.pp@bytedance.com,
Hangjing Li <lihangjing@bytedance.com>
Subject: Re: [External] Page sizes supported by RISC-V
Date: Sun, 29 Sep 2024 07:04:00 +0200 [thread overview]
Message-ID: <87o747xd8f.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAPYmKFtWPxEvD7v4FfN1n=YGuYCKgFFm7SNer5-GF95OBTMG+Q@mail.gmail.com> (Xu Lu's message of "Sun, 29 Sep 2024 11:29:11 +0800")
* Xu Lu:
> Thus, we are also trying to call for native 64K MMU in RISC-V
> community. You can find the discussion in link [1]. We hope more
> people can participate in the discussion and provide more data
> support.
If you are seriously considering offering 64K pages as an option, you
need to clarify the specifications and update binutils *today* to
increase the default maximum page size for the binaries the linker
generates. The transition will only become harder as adoption grows.
Thanks,
Florian
_______________________________________________
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 5:04 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 [this message]
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
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=87o747xd8f.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=jeffreyalaw@gmail.com \
--cc=lihangjing@bytedance.com \
--cc=linux-riscv@lists.infradead.org \
--cc=luxu.kernel@bytedance.com \
--cc=palmer@rivosinc.com \
--cc=punit.agrawal@bytedance.com \
--cc=wangpengcheng.pp@bytedance.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.