On Mon, Sep 23, 2019 at 2:21 PM Ben Cotton <bcotton@xxxxxxxxxx> wrote: > > https://fedoraproject.org/wiki/Changes/ThermalManagementWS > > == Summary == > Better thermal management and peak performance on Intel CPUs by > including thermald in the default install. > > == Owner == > * Name: [[User:benzea| Benjamin Berg]] > * Email: bberg@xxxxxxxxxx > > * Name: [[User:ckellner| Christian J. Kellner]] > * Email: ckellner@xxxxxxxxxx > * Product: Workstation > * Responsible WG: Workstation > > == Detailed Description == > > Modern Intel-based systems provide sensors and methods to monitor and > control temperature of its CPUs. The Thermal daemon will use those > sensors to monitor the temperature and use the best available method > to keep the CPU in the right temperature envelop. On certain systems > this is needed to reach the maximal performance. For optimal > performance a per-model thermald configuration should be created, this > can either be done by using dptfxtract (available from rpmfusion) or > we could ship static configuration files for a set of known models. > > For a more details explanation please consult Intel's > [https://01.org/linux-thermal-daemon/documentation/introduction-thermal-daemon > introduction] to thermald. > > == Benefit to Fedora == > > Better out-of-the-box experience due to improved cooling methods and > performance on Intel systems. > > == Scope == > * Proposal owners: > - Include the thermald package in the default Workstation install > - Optionally provide patches for thermald to be able to read hardware > specific configuration data To me this looks like a wrong order of operations: - Upstream patches to read hardware-specific configuration data - Include the thermald package in the default Workstation install Or maybe there could be a wrapper script that does the detection and generates a configuration accordingly? Carrying downstream patches without an explicit plan about upstreaming them sounds contrary to our usual upstream-first principle. > - Optionally collect hardware specific configuration data and ship it I don't understand the second optional item. > * Other developers: N/A (not a System Wide Change) > * Release engineering: > * Policies and guidelines: N/A (not a System Wide Change) > * Trademark approval: N/A (not needed for this Change) > > == Upgrade/compatibility impact == > N/A (not a System Wide Change) > > == How To Test == > > Install the packages and use e.g. turbostat to monitor the > performance. Improvements may only be visible if the non-free > dptfxtract package is also installed. > > == User Experience == > - Better performance on certain hardware > - Better cooling of CPUs on certain hardware > > -- > Ben Cotton > He / Him / His > Fedora Program Manager > Red Hat > TZ=America/Indiana/Indianapolis > _______________________________________________ > 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 _______________________________________________ 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
