On 22/02/2021 17:55, David Woodhouse wrote: > On Fri, 2021-02-12 at 14:19 -0600, Justin Forbes wrote: >>> Some things, like the AMD Radeon GPU drivers, firmware or related >>> code, appear to be completely non-functional on the 64k page size. >>> Insufficient upstream developers are testing such issues on this >>> architecture. >> >> Just as there are many things that expect the 64K page size. I am not >> doing this. > > I don't really find either of those to be compelling arguments, FWIW. > > If we have broken code which makes assumptions about page sizes, we > should fix it. Whatever assumption it makes. > > We certainly *shouldn't* have assumptions like that in userspace, and > we *shouldn't* need to rebuild userspace for such a change. > > For a long time we had 4KiB pages on ppc32 AND 64KiB pages on ppc64, > and we fixed things to use getpagesize() instead of hard-coding any > value at all. It's possible that we have regressions, but we should > probably fix those. > > Once upon a time when we still supported the PS3, the 64KiB page size > was fairly painful and inefficient there but IBM forced it because it > apparently gave a significant performance win on boxes and workloads > that they actually cared about. These days, I think the arguments for > 64KiB are certainly no *less* compelling than they were then, when I > conceded the change. I feel that you underestimate the impact of the GPU driver issue If the GPU driver doesn't work, people can't even log in and get started If the GPU vendors don't test their code on ppc64le (and aarch64) then those platforms will always lag behind x86. Users will experience issues that have been fixed in the development phase for x86. Personally, I'm not opposed to the 64k page size in principle: my concerns are about the practical issues. If both 4k and 64k can be supported, if users can choose between installers for either page size, then the severity of the issue is reduced Regards, Daniel _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
