From Fedora Project Wiki
< Features
(Created page with "<!-- The actual name of your feature page should look something like: Features/YourFeatureName. This keeps all features in the same namespace --> = Feature PowerManagementF17 =...") |
|||
| (7 intermediate revisions by 2 users not shown) | |||
| Line 4: | Line 4: | ||
== Summary == | == Summary == | ||
The goal of [[SIGs/PowerManagement]] is to improve the current state of power management in userspace. For Fedora 17 | The goal of [[SIGs/PowerManagement]] is to improve the current state of power management in userspace. For Fedora 17 our plan is to extend and improve tuned functionality. | ||
== Owner == | == Owner == | ||
| Line 15: | Line 15: | ||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/17 | Fedora 17 ]] | * Targeted release: [[Releases/17 | Fedora 17 ]] | ||
* Last updated: 2012- | * Last updated: 2012-03-20 | ||
* Percentage of completion: | * Percentage of completion: 100% | ||
<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. --> | <!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. --> | ||
| Line 22: | Line 22: | ||
== Detailed Description == | == Detailed Description == | ||
<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | <!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | ||
Tuned package contains a daemon that tunes system settings statically and dynamically according to selected profile | Tuned package contains a daemon that tunes system settings statically and dynamically according to selected profile (e.g. performance, low latency, low power consumption). In the past, profiles could be changed only from command line. Later, matahari support was implemented for remote tuning capability. Now, we would like to add dbus interface for better desktop integration. The new interface will also support "on demand" tuning, i.e. applications could signal it's requirements via dbus that would be taken into account by tuned. Next, we would like to improve current tuned profiles, add capability for creation / management of custom profiles, provide tighter integration with powertop and more. | ||
== Benefit to Fedora == | == Benefit to Fedora == | ||
<!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?--> | <!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?--> | ||
The tuned update | The planned tuned update will extend the PM tuning capability. Namely it will bring: | ||
* dbus interface for better desktop integration and "on demand" tuning, | * dbus interface for better desktop integration and "on demand" tuning, | ||
* tighter integration with powertop and creation of custom profiles from powertop reports, | * tighter integration with powertop and creation of custom profiles from powertop reports, | ||
* custom profiles management, | * custom profiles management, | ||
* improved scomes score calculation | * improved formula for scomes score calculation, | ||
* improved | * improved tuned profiles for better performance / higher power savings: | ||
** addition of KVM host/guest tuned profiles, | ** addition of KVM host/guest tuned profiles, | ||
** support for Radeon power savings, | ** support for Radeon power savings, | ||
| Line 38: | Line 38: | ||
== Scope == | == Scope == | ||
<!-- What work do the 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 the 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?--> | ||
* | * tuned needs to be reworked. So far the profile switching was performed by full restarts - this needs to be rewritten (some code changes were already made in SCM experimental branch), | ||
* powertop needs to be patched (patch was accepted by upstream). | * powertop needs to be patched (patch was accepted by upstream). | ||
| Line 59: | Line 59: | ||
# Any PC can be used for testing. For power consumption comparison (optional part), a) external wattmeter or b) laptop with functional ACPI will be needed. Users without this equipment can skip the optional part. | # Any PC can be used for testing. For power consumption comparison (optional part), a) external wattmeter or b) laptop with functional ACPI will be needed. Users without this equipment can skip the optional part. | ||
# Live-CD image with all preinstalled SW and tools will be provided. These tools will be also available from special test repository. | # Live-CD image with all preinstalled SW and tools will be provided. These tools will be also available from special test repository. | ||
# Semi automatic test cases | # Semi automatic and manual test cases with detailed instructions will be prepared. At least following test cases will be utilised: | ||
#* | #* tuned profiles switching via command line and dbus, | ||
#* creation of custom tuned profiles from existing profiles, | #* creation of custom tuned profiles from existing profiles, | ||
#* creation of tuned profiles for aggresive power savings from powertop suggestions, | #* creation of tuned profiles for aggresive power savings from powertop suggestions, | ||
| Line 92: | Line 92: | ||
[[Category: | [[Category:FeatureAcceptedF17]] | ||
<!-- When your feature page is completed and ready for review --> | <!-- When your feature page is completed and ready for review --> | ||
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler --> | <!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler --> | ||
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete--> | <!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete--> | ||
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process --> | <!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process --> | ||
Latest revision as of 07:59, 27 March 2012
Feature PowerManagementF17
Summary
The goal of SIGs/PowerManagement is to improve the current state of power management in userspace. For Fedora 17 our plan is to extend and improve tuned functionality.
Owner
- Name: Jaroslav Škarvada
- Email: jskarvad AT redhat.com
Current status
- Targeted release: Fedora 17
- Last updated: 2012-03-20
- Percentage of completion: 100%
Detailed Description
Tuned package contains a daemon that tunes system settings statically and dynamically according to selected profile (e.g. performance, low latency, low power consumption). In the past, profiles could be changed only from command line. Later, matahari support was implemented for remote tuning capability. Now, we would like to add dbus interface for better desktop integration. The new interface will also support "on demand" tuning, i.e. applications could signal it's requirements via dbus that would be taken into account by tuned. Next, we would like to improve current tuned profiles, add capability for creation / management of custom profiles, provide tighter integration with powertop and more.
Benefit to Fedora
The planned tuned update will extend the PM tuning capability. Namely it will bring:
- dbus interface for better desktop integration and "on demand" tuning,
- tighter integration with powertop and creation of custom profiles from powertop reports,
- custom profiles management,
- improved formula for scomes score calculation,
- improved tuned profiles for better performance / higher power savings:
- addition of KVM host/guest tuned profiles,
- support for Radeon power savings,
Scope
- tuned needs to be reworked. So far the profile switching was performed by full restarts - this needs to be rewritten (some code changes were already made in SCM experimental branch),
- powertop needs to be patched (patch was accepted by upstream).
How To Test
We plan to test this feature during PowerManagement test day. Detailed instructions will be provided later on the test day wiki (similary to our previous test days). Currently known details:
- Any PC can be used for testing. For power consumption comparison (optional part), a) external wattmeter or b) laptop with functional ACPI will be needed. Users without this equipment can skip the optional part.
- Live-CD image with all preinstalled SW and tools will be provided. These tools will be also available from special test repository.
- Semi automatic and manual test cases with detailed instructions will be prepared. At least following test cases will be utilised:
- tuned profiles switching via command line and dbus,
- creation of custom tuned profiles from existing profiles,
- creation of tuned profiles for aggresive power savings from powertop suggestions,
- removal of custom profiles,
- comparison of tuned profiles efficiency for various use cases (measurement / automatic benchmark).
User Experience
With default config the feature will be invisible to users. They will be able to take advantage of it when they start tuning their systems and using tuned.
Dependencies
- tuned - developed by us
- powertop - maintained by us
Contingency Plan
There is no risk if this feature wouldn't be completed by deadline. In such case we will revert to the previous release behaviour.
Documentation
Man pages and Fedora power management guide will be updated accordingly.
Release Notes
There shouldn't be anything specific. Some highlights could be selected from the 'Benefit to Fedora' chapter.