From Fedora Project Wiki
m (Change the architecture name from ppc64el to ppc64le to match what the community understands)
Line 5: Line 5:
== Summary ==
== Summary ==


On ppc64el, the kernel is currently compiled for 64k page size.
On ppc64le, the kernel is currently compiled for 64k page size.


This change proposes using the more common 4k page size.
This change proposes using the more common 4k page size.
Line 89: Line 89:
-->
-->


Better first impression for users of ppc64el workstations.
Better first impression for users of ppc64le workstations.


Users can focus on reporting ppc64el bugs without being sidetracked by page size bugs.
Users can focus on reporting ppc64le bugs without being sidetracked by page size bugs.


== Scope ==
== Scope ==

Revision as of 11:40, 9 January 2021


POWER 4k page size

Summary

On ppc64le, the kernel is currently compiled for 64k page size.

This change proposes using the more common 4k page size.

Some HPC workloads may be disadvantaged slightly. Workstation users are likely to encounter fewer bugs.

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.

Owner

Current status

  • Targeted release: Fedora 34
  • Last updated: 2021-01-09
  • FESCo issue: <will be assigned by the Wrangler>
  • Tracker bug: <will be assigned by the Wrangler>
  • Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

Feedback

Discussed several times on devel, latest here

discussed upstream in the Raptor forum

Benefit to Fedora

Better first impression for users of ppc64le workstations.

Users can focus on reporting ppc64le bugs without being sidetracked by page size bugs.

Scope

  • Proposal owners:
  • Other developers: N/A (not a System Wide Change)
  • Release engineering: #9939 (a check of an impact with Release Engineering is needed)
  • Policies and guidelines: N/A (not a System Wide Change)
  • Trademark approval: N/A (not needed for this Change)
  • Alignment with Objectives:

Upgrade/compatibility impact

N/A (not a System Wide Change)

How To Test

User Experience

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No
  • Blocks product? product

Documentation

Release Notes