From Fedora Project Wiki
Line 55: Line 55:
 
<!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. -->
 
<!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. -->
  
Discussed several times on devel, [latest here](https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/3ZBQBUN67RG6U5QHOTBHEXAKR77S3NIC/)
+
Discussed several times on devel, [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/3ZBQBUN67RG6U5QHOTBHEXAKR77S3NIC/ latest here]
  
[discussed upstream in the Raptor forum](https://forums.raptorcs.com/index.php/topic,248.msg1852.html)
+
[https://forums.raptorcs.com/index.php/topic,248.msg1852.html discussed upstream in the Raptor forum]
  
 
== Benefit to Fedora ==
 
== Benefit to Fedora ==
Line 100: Line 100:
 
<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
 
<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
  
* Release engineering: [https://pagure.io/releng/issues #Releng issue number] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
* Release engineering: [https://pagure.io/releng/issue/9939 #9939] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.  
 
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.  
 
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->
 
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->

Revision as of 00:04, 9 January 2021


POWER 4k page size

Summary

On ppc64el, 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 ppc64el workstations.

Users can focus on reporting ppc64el 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