nikon/tuned
1
0
Fork 0
Code Activity Actions

Project renamed to TuneD

Browse source 
The 'D' is now capital to clarify pronunciation.

DBus service name is kept as '/Tuned' not to break
backward compatibility.

This will also need update of downstream tests
which rely on the specific output strings containing
the name.

Signed-off-by: Jaroslav Škarvada <jskarvad@redhat.com>
This commit is contained in:
Jaroslav Škarvada 2021-03-29 01:11:42 +02:00
parent 0c0ad33025
commit 16d4acbaca
No known key found for this signature in database
GPG key ID: D8E1C00E076E840B
67 changed files with 267 additions and 267 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
CONTRIBUTING.md
View file

@ -1,10 +1,10 @@
Contributing to Tuned
Contributing to TuneD
=====================
Submitting patches
------------------
All patches should be based on the most recent revision of Tuned, which is
All patches should be based on the most recent revision of TuneD, which is
available on [GitHub](https://github.com/redhat-performance/tuned).
Patches should be created using `git` and the commit message should generally
@ -48,8 +48,8 @@ consist of three parts:
If you use `git commit -s`, `git` will add the tag for you.
Every patch should represent a single logical change. On the one hand, each
patch should be complete enough so that after applying it, the Tuned repository
remains in a consistent state and Tuned remains, to the best of the
patch should be complete enough so that after applying it, the TuneD repository
remains in a consistent state and TuneD remains, to the best of the
contributor's knowledge, completely functional (a corollary of this is that
when making fixes to your pull request on GitHub, you should include the fixes
in the commits where they logically belong rather than appending new commits).
@ -59,8 +59,8 @@ separated into individual ones.
Patches can either be submitted in the form of pull requests to the GitHub
repository, sent to the power-management (at) lists.fedoraproject.org mailing
list, or sent directly to the maintainers of the Tuned project.
list, or sent directly to the maintainers of the TuneD project.
These guidelines were inspired by the [contribution guidelines of the Linux
Kernel](https://www.kernel.org/doc/html/latest/process/submitting-patches.html).
You can find more rationale for Tuned's guidelines in that document.
You can find more rationale for TuneD's guidelines in that document.

6
README
View file

@ -1,4 +1,4 @@
Tuned: Daemon for monitoring and adaptive tuning of system devices.
TuneD: Daemon for monitoring and adaptive tuning of system devices.
(This is tuned 2.0 with a new code base. If you are looking for the older
version, please check out branch '1.0' in our Git repository.)
@ -81,7 +81,7 @@ See the file CONTRIBUTING.md for guidelines for contributing.
License
-------
Copyright (C) 2008-2019 Red Hat, Inc.
Copyright (C) 2008-2021 Red Hat, Inc.
This program is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License
@ -105,6 +105,6 @@ differently, see the file for the text of the license.
The icon:
The Tuned icon was created by Mariia Leonova <mleonova@redhat.com> and it is
The TuneD icon was created by Mariia Leonova <mleonova@redhat.com> and it is
licensed under Creative Commons Attribution-ShareAlike 3.0 license
(http://creativecommons.org/licenses/by-sa/3.0/legalcode).

8
bootcmdline
View file

@ -1,12 +1,12 @@
# This file specifies additional parameters to kernel boot command line and
# initrd overlay images. Its content is set by the Tuned bootloader plugin
# initrd overlay images. Its content is set by the TuneD bootloader plugin
# and sourced by the grub2-mkconfig (/etc/grub.d/00_tuned script).
#
# Please do not edit this file. Content of this file can be overwritten by
# switch of Tuned profile.
# switch of TuneD profile.
#
# If you need to add parameters to the kernel boot command line, create
# Tuned profile containing the following:
# TuneD profile containing the following:
#
# [bootloader]
# cmdline = YOUR_ADDITIONAL_KERNEL_PARAMETERS
@ -22,7 +22,7 @@
#
# YOUR_ADDITIONAL_KERNEL_PARAMETERS will stay preserved.
#
# Similarly if you need to add initrd overlay image, create Tuned profile
# Similarly if you need to add initrd overlay image, create TuneD profile
# containing the following:
#
# [bootloader]

60
com.redhat.tuned.policy
View file

@ -3,7 +3,7 @@
"http://www.freedesktop.org/software/polkit/policyconfig-1.dtd">
<policyconfig>
<vendor>Tuned</vendor>
<vendor>TuneD</vendor>
<vendor_url>https://fedorahosted.org/tuned/</vendor_url>
<icon_name>tuned</icon_name>
@ -38,8 +38,8 @@
</action>
<action id="com.redhat.tuned.disable">
<description>Disable Tuned</description>
<message>Authentication is required to disable Tuned</message>
<description>Disable TuneD</description>
<message>Authentication is required to disable TuneD</message>
<defaults>
<allow_any>auth_admin</allow_any>
<allow_inactive>auth_admin</allow_inactive>
@ -48,8 +48,8 @@
</action>
<action id="com.redhat.tuned.is_running">
<description>Check whether Tuned is running</description>
<message>Authentication is required to check whether Tuned is running</message>
<description>Check whether TuneD is running</description>
<message>Authentication is required to check whether TuneD is running</message>
<defaults>
<allow_any>yes</allow_any>
<allow_inactive>yes</allow_inactive>
@ -58,8 +58,8 @@
</action>
<action id="com.redhat.tuned.profile_info">
<description>Show information about Tuned profile</description>
<message>Authentication is required to show information about Tuned profile</message>
<description>Show information about TuneD profile</description>
<message>Authentication is required to show information about TuneD profile</message>
<defaults>
<allow_any>yes</allow_any>
<allow_inactive>yes</allow_inactive>
@ -68,8 +68,8 @@
</action>
<action id="com.redhat.tuned.profiles">
<description>List Tuned profiles</description>
<message>Authentication is required to list Tuned profiles</message>
<description>List TuneD profiles</description>
<message>Authentication is required to list TuneD profiles</message>
<defaults>
<allow_any>yes</allow_any>
<allow_inactive>yes</allow_inactive>
@ -78,8 +78,8 @@
</action>
<action id="com.redhat.tuned.profiles2">
<description>List Tuned profiles</description>
<message>Authentication is required to list Tuned profiles</message>
<description>List TuneD profiles</description>
<message>Authentication is required to list TuneD profiles</message>
<defaults>
<allow_any>yes</allow_any>
<allow_inactive>yes</allow_inactive>
@ -88,7 +88,7 @@
</action>
<action id="com.redhat.tuned.recommend_profile">
<description>Show Tuned profile name which is recommended for your system</description>
<description>Show TuneD profile name which is recommended for your system</description>
<message>Authentication is required to show recommended profile name</message>
<defaults>
<allow_any>yes</allow_any>
@ -98,8 +98,8 @@
</action>
<action id="com.redhat.tuned.reload">
<description>Reload Tuned configuration</description>
<message>Authentication is required to reload Tuned configuration</message>
<description>Reload TuneD configuration</description>
<message>Authentication is required to reload TuneD configuration</message>
<defaults>
<allow_any>auth_admin</allow_any>
<allow_inactive>auth_admin</allow_inactive>
@ -108,8 +108,8 @@
</action>
<action id="com.redhat.tuned.start">
<description>Start Tuned daemon</description>
<message>Authentication is required to start Tuned daemon</message>
<description>Start TuneD daemon</description>
<message>Authentication is required to start TuneD daemon</message>
<defaults>
<allow_any>auth_admin</allow_any>
<allow_inactive>auth_admin</allow_inactive>
@ -118,8 +118,8 @@
</action>
<action id="com.redhat.tuned.stop">
<description>Stop Tuned daemon</description>
<message>Authentication is required to stop Tuned daemon</message>
<description>Stop TuneD daemon</description>
<message>Authentication is required to stop TuneD daemon</message>
<defaults>
<allow_any>auth_admin</allow_any>
<allow_inactive>auth_admin</allow_inactive>
@ -128,8 +128,8 @@
</action>
<action id="com.redhat.tuned.switch_profile">
<description>Switch Tuned profile</description>
<message>Authentication is required to switch Tuned profile</message>
<description>Switch TuneD profile</description>
<message>Authentication is required to switch TuneD profile</message>
<defaults>
<allow_any>auth_admin</allow_any>
<allow_inactive>auth_admin</allow_inactive>
@ -168,8 +168,8 @@
</action>
<action id="com.redhat.tuned.verify_profile">
<description>Verify Tuned profile</description>
<message>Authentication is required to verify Tuned profile</message>
<description>Verify TuneD profile</description>
<message>Authentication is required to verify TuneD profile</message>
<defaults>
<allow_any>yes</allow_any>
<allow_inactive>yes</allow_inactive>
@ -178,8 +178,8 @@
</action>
<action id="com.redhat.tuned.verify_profile_ignore_missing">
<description>Verify Tuned profile, ignore missing values</description>
<message>Authentication is required to verify Tuned profile</message>
<description>Verify TuneD profile, ignore missing values</description>
<message>Authentication is required to verify TuneD profile</message>
<defaults>
<allow_any>yes</allow_any>
<allow_inactive>yes</allow_inactive>
@ -188,8 +188,8 @@
</action>
<action id="com.redhat.tuned.get_all_plugins">
<description>Get plugins which Tuned daemon can acces</description>
<message>Authentication is required to get Tuned plugins</message>
<description>Get plugins which TuneD daemon can acces</description>
<message>Authentication is required to get TuneD plugins</message>
<defaults>
<allow_any>auth_admin</allow_any>
<allow_inactive>auth_admin</allow_inactive>
@ -198,8 +198,8 @@
</action>
<action id="com.redhat.tuned.get_plugin_documentation">
<description>Get documentation of tuned plugin</description>
<message>Authentication is required to get documentation of tuned plugin</message>
<description>Get documentation of TuneD plugin</description>
<message>Authentication is required to get documentation of TuneD plugin</message>
<defaults>
<allow_any>auth_admin</allow_any>
<allow_inactive>auth_admin</allow_inactive>
@ -208,8 +208,8 @@
</action>
<action id="com.redhat.tuned.get_plugin_hints">
<description>Get hints for parameters of Tuned plugin</description>
<message>Authentication is required to get hints for parameters of Tuned plugin</message>
<description>Get hints for parameters of TuneD plugin</description>
<message>Authentication is required to get hints for parameters of TuneD plugin</message>
<defaults>
<allow_any>auth_admin</allow_any>
<allow_inactive>auth_admin</allow_inactive>

2
contrib/sysvinit/tuned
View file

@ -10,7 +10,7 @@
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# X-Interactive: false
# Short-Description: Tuned daemon
# Short-Description: TuneD daemon
# Description: Dynamic System Tuning Daemon
### END INIT INFO
# PATH should only include /usr/* if it runs after the mountnfs.sh script

10
doc/manual/README.adoc
View file

@ -1,6 +1,6 @@
= About this documentation
This directory contains source files of Tuned documentation intended for system administrators.
This directory contains source files of TuneD documentation intended for system administrators.
== Building the source
@ -18,16 +18,16 @@ The `master.adoc` file is the main entry point for the documentation. It _includ
== Naming conventions
Use the following naming conventions when referring to Tuned and its components in the documentation:
Use the following naming conventions when referring to TuneD and its components in the documentation:
* "the *Tuned* application", referring to the complete set of software, including executables, profiles, scripts, documentation, artwork, etc. Written as `the \*Tuned* application` in AsciiDoc, because application names are in bold text.
* "the *TuneD* application", referring to the complete set of software, including executables, profiles, scripts, documentation, artwork, etc. Written as `the \*TuneD* application` in AsciiDoc, because application names are in bold text.
* "the Tuned project", referring to the developers and contributors, the web pages, repositories, planning, etc.
* "the TuneD project", referring to the developers and contributors, the web pages, repositories, planning, etc.
* "the `tuned` service", referring to the `tuned.service` systemd unit and the `tuned` executable
* "the `tuned-adm` utility", referring to the `tuned-adm` executable
* "the `tuned` and `tuned-adm` commands", referring to the text typed into the terminal to run components of Tuned
* "the `tuned` and `tuned-adm` commands", referring to the text typed into the terminal to run components of TuneD
This is consistent with other naming schemes. For example, consider "the Firefox application" vs. "the `firefox` command".

8
doc/manual/assemblies/assembly_customizing-tuned-profiles.adoc
View file

@ -1,15 +1,15 @@
:parent-context-of-customizing-tuned-profiles: {context}
[id='customizing-tuned-profiles_{context}']
= Customizing Tuned profiles
= Customizing TuneD profiles
:context: customizing-tuned-profiles
You can create or modify *Tuned* profiles to optimize system performance for your intended use case.
You can create or modify *TuneD* profiles to optimize system performance for your intended use case.
.Prerequisites
* Install and enable *Tuned* as described in xref:installing-and-enabling-tuned_getting-started-with-tuned[].
* Install and enable *TuneD* as described in xref:installing-and-enabling-tuned_getting-started-with-tuned[].
include::modules/performance/con_tuned-profiles.adoc[leveloffset=+1]
@ -37,6 +37,6 @@ include::modules/performance/proc_setting-the-disk-scheduler-using-tuned.adoc[le
== Related information
* The `tuned.conf(5)` man page
* The *Tuned* project website: link:https://tuned-project.org/[]
* The *TuneD* project website: link:https://tuned-project.org/[]
:context: {parent-context-of-customizing-tuned-profiles}

6
doc/manual/assemblies/assembly_getting-started-with-tuned.adoc
View file

@ -1,11 +1,11 @@
:parent-context-of-getting-started-with-tuned: {context}
[id='getting-started-with-tuned_{context}']
= Getting started with Tuned
= Getting started with TuneD
:context: getting-started-with-tuned
As a system administrator, you can use the *Tuned* application to optimize the performance profile of your system for a variety of use cases.
As a system administrator, you can use the *TuneD* application to optimize the performance profile of your system for a variety of use cases.
// .Prerequisites
//
@ -38,6 +38,6 @@ include::modules/performance/proc_disabling-tuned.adoc[leveloffset=+1]
* The `tuned(8)` man page
* The `tuned-adm(8)` man page
* The *Tuned* project website: link:https://tuned-project.org/[]
* The *TuneD* project website: link:https://tuned-project.org/[]
:context: {parent-context-of-getting-started-with-tuned}

6
doc/manual/master.adoc
View file

@ -3,10 +3,10 @@
:keywords: documentation, tuned, performance, power, linux
:toc:
// The revnumber attribute is intended to show the Tuned version for which the document has been updated
// The revnumber attribute is intended to show the TuneD version for which the document has been updated
[id="{tuned-documentation}"]
= Tuned documentation: Optimizing system throughput, latency, and power consumption
= TuneD documentation: Optimizing system throughput, latency, and power consumption
// Load externally defined attributes
include::meta/attributes.adoc[]
@ -19,7 +19,7 @@ include::meta/attributes.adoc[]
// Abstract (Preamble):
This documentation explains how to use the *Tuned* application to monitor and optimize the throughput, latency, and power consumption of your system in different scenarios.
This documentation explains how to use the *TuneD* application to monitor and optimize the throughput, latency, and power consumption of your system in different scenarios.
// The following is copied from the standard Red Hat legal notice
// as used in all Red Hat documentation.

8
doc/manual/modules/performance/con_inheritance-between-tuned-profiles.adoc
View file

@ -1,9 +1,9 @@
[id="inheritance-between-tuned-profiles_{context}"]
= Inheritance between Tuned profiles
= Inheritance between TuneD profiles
*Tuned* profiles can be based on other profiles and modify only certain aspects of their parent profile.
*TuneD* profiles can be based on other profiles and modify only certain aspects of their parent profile.
The `[main]` section of *Tuned* profiles recognizes the [option]`include` option:
The `[main]` section of *TuneD* profiles recognizes the [option]`include` option:
[subs=+quotes]
----
@ -15,7 +15,7 @@ All settings from the [replaceable]_parent_ profile are loaded in this _child_ p
You can create your own _child_ profile in the [filename]`/etc/tuned/` directory based on a pre-installed profile in [filename]`/usr/lib/tuned/` with only some parameters adjusted.
If the [replaceable]_parent_ profile is updated, such as after a *Tuned* upgrade, the changes are reflected in the _child_ profile.
If the [replaceable]_parent_ profile is updated, such as after a *TuneD* upgrade, the changes are reflected in the _child_ profile.
.A power-saving profile based on balanced

16
doc/manual/modules/performance/con_static-and-dynamic-tuning-in-tuned.adoc
View file

@ -1,7 +1,7 @@
[id="static-and-dynamic-tuning-in-tuned_{context}"]
= Static and dynamic tuning in Tuned
= Static and dynamic tuning in TuneD
This section explains the difference between the two categories of system tuning that *Tuned* applies: _static_ and _dynamic_.
This section explains the difference between the two categories of system tuning that *TuneD* applies: _static_ and _dynamic_.
// TODO: Move some of this content into a separate module ("Enabling dynamic tuning"). It seems to be necessary to (1) enable dynamic tuning globally *and* (2) manually enable it in performance-oriented profiles.
@ -9,13 +9,13 @@ Static tuning::
Mainly consists of the application of predefined `sysctl` and `sysfs` settings and one-shot activation of several configuration tools such as `ethtool`.
Dynamic tuning::
Watches how various system components are used throughout the uptime of your system. *Tuned* adjusts system settings dynamically based on that monitoring information.
Watches how various system components are used throughout the uptime of your system. *TuneD* adjusts system settings dynamically based on that monitoring information.
+
For example, the hard drive is used heavily during startup and login, but is barely used later when the user might mainly work with applications such as web browsers or email clients. Similarly, the CPU and network devices are used differently at different times. *Tuned* monitors the activity of these components and reacts to the changes in their use.
For example, the hard drive is used heavily during startup and login, but is barely used later when the user might mainly work with applications such as web browsers or email clients. Similarly, the CPU and network devices are used differently at different times. *TuneD* monitors the activity of these components and reacts to the changes in their use.
+
By default, dynamic tuning is disabled. To enable it, edit the [filename]`/etc/tuned/tuned-main.conf` file and change the [option]`dynamic_tuning` option to `1`. *Tuned* then periodically analyzes system statistics and uses them to update your system tuning settings. To configure the time interval in seconds between these updates, use the [option]`update_interval` option.
By default, dynamic tuning is disabled. To enable it, edit the [filename]`/etc/tuned/tuned-main.conf` file and change the [option]`dynamic_tuning` option to `1`. *TuneD* then periodically analyzes system statistics and uses them to update your system tuning settings. To configure the time interval in seconds between these updates, use the [option]`update_interval` option.
+
Currently implemented dynamic tuning algorithms try to balance the performance and powersave, and are therefore disabled in the performance profiles. Dynamic tuning for individual plug-ins can be enabled or disabled in the *Tuned* profiles.
Currently implemented dynamic tuning algorithms try to balance the performance and powersave, and are therefore disabled in the performance profiles. Dynamic tuning for individual plug-ins can be enabled or disabled in the *TuneD* profiles.
// Internal note: Dynamic tuning is still disabled as of RHEL 8.0 Beta.
@ -23,9 +23,9 @@ Currently implemented dynamic tuning algorithms try to balance the performance a
====
On a typical office workstation, the Ethernet network interface is inactive most of the time. Only a few emails go in and out or some web pages might be loaded.
For those kinds of loads, the network interface does not have to run at full speed all the time, as it does by default. *Tuned* has a monitoring and tuning plug-in for network devices that can detect this low activity and then automatically lower the speed of that interface, typically resulting in a lower power usage.
For those kinds of loads, the network interface does not have to run at full speed all the time, as it does by default. *TuneD* has a monitoring and tuning plug-in for network devices that can detect this low activity and then automatically lower the speed of that interface, typically resulting in a lower power usage.
If the activity on the interface increases for a longer period of time, for example because a DVD image is being downloaded or an email with a large attachment is opened, *Tuned* detects this and sets the interface speed to maximum to offer the best performance while the activity level is high.
If the activity on the interface increases for a longer period of time, for example because a DVD image is being downloaded or an email with a large attachment is opened, *TuneD* detects this and sets the interface speed to maximum to offer the best performance while the activity level is high.
This principle is used for other plug-ins for CPU and disks as well.
====

12
doc/manual/modules/performance/con_the-purpose-of-tuned.adoc
View file

@ -1,19 +1,19 @@
[id="the-purpose-of-tuned_{context}"]
= The purpose of Tuned
= The purpose of TuneD
*Tuned* is a service that monitors your system and optimizes the performance under certain workloads. The core of *Tuned* are _profiles_, which tune your system for different use cases.
*TuneD* is a service that monitors your system and optimizes the performance under certain workloads. The core of *TuneD* are _profiles_, which tune your system for different use cases.
*Tuned* is distributed with a number of predefined profiles for use cases such as:
*TuneD* is distributed with a number of predefined profiles for use cases such as:
* High throughput
* Low latency
* Saving power
It is possible to modify the rules defined for each profile and customize how to tune a particular device. When you switch to another profile or deactivate *Tuned*, all changes made to the system settings by the previous profile revert back to their original state.
It is possible to modify the rules defined for each profile and customize how to tune a particular device. When you switch to another profile or deactivate *TuneD*, all changes made to the system settings by the previous profile revert back to their original state.
You can also configure *Tuned* to react to changes in device usage and adjusts settings to improve performance of active devices and reduce power consumption of inactive devices.
You can also configure *TuneD* to react to changes in device usage and adjusts settings to improve performance of active devices and reduce power consumption of inactive devices.
// The tuned tuning service can adapt the operating system to perform better under certain workloads by setting a tuning profile.
// The TuneD tuning service can adapt the operating system to perform better under certain workloads by setting a tuning profile.
// .Additional resources
//

6
doc/manual/modules/performance/con_tuned-no-daemon-mode.adoc
View file

@ -1,11 +1,11 @@
[id="tuned-no-daemon-mode_{context}"]
= Tuned no-daemon mode
= TuneD no-daemon mode
// TODO: Should this be a procedure? A user story? Is there a common use case?
You can run *Tuned* in `no-daemon` mode, which does not require any resident memory. In this mode, *Tuned* applies the settings and exits.
You can run *TuneD* in `no-daemon` mode, which does not require any resident memory. In this mode, *TuneD* applies the settings and exits.
By default, `no-daemon` mode is disabled because a lot of *Tuned* functionality is missing in this mode, including:
By default, `no-daemon` mode is disabled because a lot of *TuneD* functionality is missing in this mode, including:
* D-Bus support
* Hot-plug support

14
doc/manual/modules/performance/con_tuned-plug-ins.adoc
View file

@ -1,9 +1,9 @@
[id="tuned-plug-ins_{context}"]
= Tuned plug-ins
= TuneD plug-ins
Plug-ins are modules in *Tuned* profiles that *Tuned* uses to monitor or optimize different devices on the system.
Plug-ins are modules in *TuneD* profiles that *TuneD* uses to monitor or optimize different devices on the system.
*Tuned* uses two types of plug-ins:
*TuneD* uses two types of plug-ins:
* monitoring plug-ins
* tuning plug-ins
@ -18,10 +18,10 @@ Monitoring plug-ins are automatically instantiated whenever their metrics are ne
[discrete]
== Tuning plug-ins
Each tuning plug-in tunes an individual subsystem and takes several parameters that are populated from the tuned profiles. Each subsystem can have multiple devices, such as multiple CPUs or network cards, that are handled by individual instances of the tuning plug-ins. Specific settings for individual devices are also supported.
Each tuning plug-in tunes an individual subsystem and takes several parameters that are populated from the TuneD profiles. Each subsystem can have multiple devices, such as multiple CPUs or network cards, that are handled by individual instances of the tuning plug-ins. Specific settings for individual devices are also supported.
[discrete]
== Syntax for plug-ins in Tuned profiles
== Syntax for plug-ins in TuneD profiles
Sections describing plug-in instances are formatted in the following way:
@ -72,7 +72,7 @@ If the plug-in supports more options, they can be also specified in the plug-in
[discrete]
== Short plug-in syntax
If you do not need custom names for the plug-in instance and there is only one definition of the instance in your configuration file, *Tuned* supports the following short syntax:
If you do not need custom names for the plug-in instance and there is only one definition of the instance in your configuration file, *TuneD* supports the following short syntax:
[subs=quotes]
----
@ -101,7 +101,7 @@ You can also disable the plug-in by specifying the [option]`enabled=false` optio
[discrete]
== Functionality not implemented in any plug-in
*Tuned* includes the ability to run any shell command as part of enabling or disabling a tuning profile. This enables you to extend *Tuned* profiles with functionality that has not been integrated into Tuned yet.
*TuneD* includes the ability to run any shell command as part of enabling or disabling a tuning profile. This enables you to extend *TuneD* profiles with functionality that has not been integrated into TuneD yet.
You can specify arbitrary shell commands using the `script` plug-in.

10
doc/manual/modules/performance/con_tuned-profiles.adoc
View file

@ -1,9 +1,9 @@
[id="tuned-profiles_{context}"]
= Tuned profiles
= TuneD profiles
A detailed analysis of a system can be very time-consuming. *Tuned* provides a number of predefined profiles for typical use cases. You can also create, modify, and delete profiles.
A detailed analysis of a system can be very time-consuming. *TuneD* provides a number of predefined profiles for typical use cases. You can also create, modify, and delete profiles.
The profiles provided with *Tuned* are divided into the following categories:
The profiles provided with *TuneD* are divided into the following categories:
* Power-saving profiles
* Performance-boosting profiles
@ -32,7 +32,7 @@ During the installation, the best profile for your system is selected automatica
[discrete]
== Merged profiles
As an experimental feature, it is possible to select more profiles at once. *Tuned* will try to merge them during the load.
As an experimental feature, it is possible to select more profiles at once. *TuneD* will try to merge them during the load.
If there are conflicts, the settings from the last specified profile takes precedence.
@ -50,7 +50,7 @@ WARNING: Merging is done automatically without checking whether the resulting co
[discrete]
== The location of profiles
*Tuned* stores profiles in the following directories:
*TuneD* stores profiles in the following directories:
[filename]`/usr/lib/tuned/`::
Distribution-specific profiles are stored in the directory. Each profile has its own directory. The profile consists of the main configuration file called `tuned.conf`, and optionally other files, for example helper scripts.

12
doc/manual/modules/performance/con_variables-and-built-in-functions-in-tuned-profiles.adoc
View file

@ -1,17 +1,17 @@
[id="variables-and-built-in-functions-in-tuned-profiles_{context}"]
= Variables and built-in functions in Tuned profiles
= Variables and built-in functions in TuneD profiles
Variables and built-in functions expand at run time when a *Tuned* profile is activated.
Variables and built-in functions expand at run time when a *TuneD* profile is activated.
Using *Tuned* variables reduces the amount of necessary typing in *Tuned* profiles. You can also:
Using *TuneD* variables reduces the amount of necessary typing in *TuneD* profiles. You can also:
* Use various built-in functions together with *Tuned* variables
* Create custom functions in Python and add them to *Tuned* in the form of plug-ins
* Use various built-in functions together with *TuneD* variables
* Create custom functions in Python and add them to *TuneD* in the form of plug-ins
[discrete]
== Variables
There are no predefined variables in *Tuned* profiles. You can define your own variables by creating the `[variables]` section in a profile and using the following syntax:
There are no predefined variables in *TuneD* profiles. You can define your own variables by creating the `[variables]` section in a profile and using the following syntax:
[subs=+quotes]
----

10
doc/manual/modules/performance/proc_creating-new-tuned-profiles.adoc
View file

@ -1,7 +1,7 @@
[id="creating-new-tuned-profiles_{context}"]
= Creating new Tuned profiles
= Creating new TuneD profiles
This procedure creates a new *Tuned* profile with custom performance rules.
This procedure creates a new *TuneD* profile with custom performance rules.
.Prerequisites
@ -22,7 +22,7 @@ For example, see the configuration of the `balanced` profile:
+
----
[main]
summary=General non-specialized tuned profile
summary=General non-specialized TuneD profile
[cpu]
governor=conservative
@ -45,7 +45,7 @@ alpm=medium_power
# tuned-adm profile [replaceable]_my-profile_
----
. Verify that the *Tuned* profile is active and the system settings are applied:
. Verify that the *TuneD* profile is active and the system settings are applied:
+
[subs=+quotes]
----
@ -58,7 +58,7 @@ Current active profile: [replaceable]_my-profile_
$ tuned-adm verify
Verfication succeeded, current system settings match the preset profile.
See tuned log file ('/var/log/tuned/tuned.log') for details.
See TuneD log file ('/var/log/tuned/tuned.log') for details.
----
.Additional resources

4
doc/manual/modules/performance/proc_disabling-tuned.adoc
View file

@ -1,7 +1,7 @@
[id="disabling-tuned_{context}"]
= Disabling Tuned
= Disabling TuneD
This procedure disables *Tuned* and resets all affected system settings to their original state before *Tuned* modified them.
This procedure disables *TuneD* and resets all affected system settings to their original state before *TuneD* modified them.
// .Prerequisites
//

10
doc/manual/modules/performance/proc_installing-and-enabling-tuned.adoc
View file

@ -1,7 +1,7 @@
[id="installing-and-enabling-tuned_{context}"]
= Installing and enabling Tuned
= Installing and enabling TuneD
This procedure installs and enables the *Tuned* application, installs *Tuned* profiles, and presets a default *Tuned* profile for your system.
This procedure installs and enables the *TuneD* application, installs *TuneD* profiles, and presets a default *TuneD* profile for your system.
// .Prerequisites
//
@ -23,13 +23,13 @@ This procedure installs and enables the *Tuned* application, installs *Tuned* pr
# systemctl enable --now tuned
----
. Optionally, install *Tuned* profiles for real-time systems:
. Optionally, install *TuneD* profiles for real-time systems:
+
----
# yum install tuned-profiles-realtime tuned-profiles-nfv
----
. Verify that a *Tuned* profile is active and applied:
. Verify that a *TuneD* profile is active and applied:
+
[subs=+quotes]
----
@ -42,7 +42,7 @@ Current active profile: [replaceable]_balanced_
$ tuned-adm verify
Verfication succeeded, current system settings match the preset profile.
See tuned log file ('/var/log/tuned/tuned.log') for details.
See TuneD log file ('/var/log/tuned/tuned.log') for details.
----

6
doc/manual/modules/performance/proc_listing-available-tuned-profiles.adoc
View file

@ -1,7 +1,7 @@
[id="listing-available-tuned-profiles_{context}"]
= Listing available Tuned profiles
= Listing available TuneD profiles
This procedure lists all *Tuned* profiles that are currently available on your system.
This procedure lists all *TuneD* profiles that are currently available on your system.
//No prerequisites are needed
////
@ -12,7 +12,7 @@ This procedure lists all *Tuned* profiles that are currently available on your s
.Procedure
* To list all available *Tuned* profiles on your system, use:
* To list all available *TuneD* profiles on your system, use:
+
[subs="+quotes",options="+nowrap",role=white-space-pre]
----

10
doc/manual/modules/performance/proc_modifying-existing-tuned-profiles.adoc
View file

@ -1,7 +1,7 @@
[id="modifying-existing-tuned-profiles_{context}"]
= Modifying existing Tuned profiles
= Modifying existing TuneD profiles
This procedure creates a modified child profile based on an existing *Tuned* profile.
This procedure creates a modified child profile based on an existing *TuneD* profile.
.Prerequisites
@ -50,7 +50,7 @@ vm.swappiness=5
# tuned-adm profile [replaceable]_modified-profile_
----
. Verify that the *Tuned* profile is active and the system settings are applied:
. Verify that the *TuneD* profile is active and the system settings are applied:
+
[subs=+quotes]
----
@ -63,7 +63,7 @@ Current active profile: [replaceable]_my-profile_
$ tuned-adm verify
Verfication succeeded, current system settings match the preset profile.
See tuned log file ('/var/log/tuned/tuned.log') for details.
See TuneD log file ('/var/log/tuned/tuned.log') for details.
----
// .An alternative approach
@ -73,7 +73,7 @@ See tuned log file ('/var/log/tuned/tuned.log') for details.
// # cp -r /usr/lib/tuned/throughput-performance /etc/tuned
// ----
//
// . Then, edit the profile in /etc/tuned according to your needs. Note that if there are two profiles of the same name, the profile located in /etc/tuned/ is loaded. The disadvantage of this approach is that if a system profile is updated after a tuned upgrade, the changes will not be reflected in the now-outdated modified version.
// . Then, edit the profile in /etc/tuned according to your needs. Note that if there are two profiles of the same name, the profile located in /etc/tuned/ is loaded. The disadvantage of this approach is that if a system profile is updated after a TuneD upgrade, the changes will not be reflected in the now-outdated modified version.
.Additional resources

12
doc/manual/modules/performance/proc_setting-a-tuned-profile.adoc
View file

@ -1,7 +1,7 @@
[id="setting-a-tuned-profile_{context}"]
= Setting a Tuned profile
= Setting a TuneD profile
This procedure activates a selected *Tuned* profile on your system.
This procedure activates a selected *TuneD* profile on your system.
.Prerequisites
@ -9,7 +9,7 @@ This procedure activates a selected *Tuned* profile on your system.
.Procedure
. Optionally, you can let *Tuned* recommend the most suitable profile for your system:
. Optionally, you can let *TuneD* recommend the most suitable profile for your system:
+
[subs=+quotes]
----
@ -41,7 +41,7 @@ The following example optimizes the system to run in a virtual machine with the
----
====
. View the current active *Tuned* profile on your system:
. View the current active *TuneD* profile on your system:
+
[subs=+quotes]
----
@ -58,13 +58,13 @@ Current active profile: [replaceable]_selected-profile_
.Verification steps
* Verify that the *Tuned* profile is active and applied:
* Verify that the *TuneD* profile is active and applied:
+
----
$ tuned-adm verify
Verfication succeeded, current system settings match the preset profile.
See tuned log file ('/var/log/tuned/tuned.log') for details.
See TuneD log file ('/var/log/tuned/tuned.log') for details.
----

20
doc/manual/modules/performance/proc_setting-the-disk-scheduler-using-tuned.adoc
View file

@ -1,7 +1,7 @@
[id="setting-the-disk-scheduler-using-tuned_{context}"]
= Setting the disk scheduler using Tuned
= Setting the disk scheduler using TuneD
This procedure creates and enables a *Tuned* profile that sets a given disk scheduler for selected block devices. The setting persists across system reboots.
This procedure creates and enables a *TuneD* profile that sets a given disk scheduler for selected block devices. The setting persists across system reboots.
In the following commands and configuration, replace:
@ -10,7 +10,7 @@ In the following commands and configuration, replace:
.Prerequisites
// Use an xref if we're inside the performance title or the upstream Tuned manual.
// Use an xref if we're inside the performance title or the upstream TuneD manual.
ifdef::performance-title[]
:installing-tuned-link: pass:macros[xref:installing-and-enabling-tuned_getting-started-with-tuned[]]
endif::[]
@ -29,7 +29,7 @@ For details, see {installing-tuned-link}.
.Procedure
// Use an xref if we're inside the performance title or the upstream Tuned manual.
// Use an xref if we're inside the performance title or the upstream TuneD manual.
ifdef::performance-title[]
:tuned-profiles-link: pass:macros[xref:tuned-profiles-distributed-with-rhel_getting-started-with-tuned[]]
endif::[]
@ -42,7 +42,7 @@ ifndef::performance-title[]
:tuned-profiles-link: pass:macros[https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/monitoring_and_managing_system_status_and_performance/getting-started-with-tuned_monitoring-and-managing-system-status-and-performance#tuned-profiles-distributed-with-rhel_getting-started-with-tuned]
endif::[]
. Optional: Select an existing *Tuned* profile on which your profile will be based. For a list of available profiles, see {tuned-profiles-link}.
. Optional: Select an existing *TuneD* profile on which your profile will be based. For a list of available profiles, see {tuned-profiles-link}.
+
To see which profile is currently active, use:
+
@ -50,7 +50,7 @@ To see which profile is currently active, use:
$ tuned-adm active
----
. Create a new directory to hold your *Tuned* profile:
. Create a new directory to hold your *TuneD* profile:
+
[subs=+quotes]
----
@ -99,7 +99,7 @@ devices_udev_regex=(ID_WWN=[replaceable]__0x5002538d00000000__)|(ID_WWN=[replace
# tuned-adm profile [replaceable]__my-profile__
----
. Verify that the Tuned profile is active and applied:
. Verify that the TuneD profile is active and applied:
+
[subs=+quotes]
----
@ -112,13 +112,13 @@ Current active profile: [replaceable]_my-profile_
$ tuned-adm verify
Verification succeeded, current system settings match the preset profile.
See tuned log file ('/var/log/tuned/tuned.log') for details.
See TuneD log file ('/var/log/tuned/tuned.log') for details.
----
.Additional resources
// Use an xref if we're inside the performance title or the upstream Tuned manual.
// Use an xref if we're inside the performance title or the upstream TuneD manual.
ifdef::performance-title[]
:customizing-tuned-link: pass:macros[xref:customizing-tuned-profiles_monitoring-and-managing-system-status-and-performance[]]
endif::[]
@ -131,5 +131,5 @@ ifndef::performance-title[]
:customizing-tuned-link: pass:macros[https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/monitoring_and_managing_system_status_and_performance/customizing-tuned-profiles_monitoring-and-managing-system-status-and-performance]
endif::[]
* For more information on creating a *Tuned* profile, see {customizing-tuned-link}.
* For more information on creating a *TuneD* profile, see {customizing-tuned-link}.

22
doc/manual/modules/performance/ref_available-tuned-plug-ins.adoc
View file

@ -1,7 +1,7 @@
[id="available-tuned-plug-ins_{context}"]
= Available Tuned plug-ins
= Available TuneD plug-ins
This section lists all monitoring and tuning plug-ins currently available in *Tuned*.
This section lists all monitoring and tuning plug-ins currently available in *TuneD*.
[discrete]
== Monitoring plug-ins
@ -36,7 +36,7 @@ This feature can be found on some netbooks and is also known as the ASUS Super H
+
If the CPU load is lower or equal to the value specified by the [option]`load_threshold_powersave` option, the plug-in sets the FSB speed to the value specified by the [option]`she_powersave` option. If the CPU load is higher or equal to the value specified by the [option]`load_threshold_normal` option, it sets the FSB speed to the value specified by the [option]`she_normal` option.
+
Static tuning is not supported and the plug-in is transparently disabled if *Tuned* does not detect the hardware support for this feature.
Static tuning is not supported and the plug-in is transparently disabled if *TuneD* does not detect the hardware support for this feature.
`net`::
Configures the Wake-on-LAN functionality to the values specified by the [option]`wake_on_lan` option. It uses the same syntax as the `ethtool` utility. It also dynamically changes the interface speed according to the interface utilization.
@ -46,7 +46,7 @@ Sets various `sysctl` settings specified by the plug-in options.
+
The syntax is ``[replaceable]__name__=[replaceable]__value__``, where [replaceable]_name_ is the same as the name provided by the `sysctl` utility.
+
Use the `sysctl` plug-in if you need to change system settings that are not covered by other plug-ins available in *Tuned*. If the settings are covered by some specific plug-ins, prefer these plug-ins.
Use the `sysctl` plug-in if you need to change system settings that are not covered by other plug-ins available in *TuneD*. If the settings are covered by some specific plug-ins, prefer these plug-ins.
`usb`::
Sets autosuspend timeout of USB devices to the value specified by the [option]`autosuspend` parameter.
@ -100,7 +100,7 @@ can be set with the `perf_mmap_pages` parameter. Value of this parameter has to
the nearest bigger power of 2 value is calculated from it and this calculated value is used. If the `perf_mmap_pages`
parameter is omitted, the default kernel value is used, which should be 128 for the recent kernels (tested on kernel-5.9.8).
+
The `default_irq_smp_affinity` parameter controls the values *Tuned* writes to `/proc/irq/default_smp_affinity`.
The `default_irq_smp_affinity` parameter controls the values *TuneD* writes to `/proc/irq/default_smp_affinity`.
The following values are supported:
+
--
@ -111,7 +111,7 @@ and the previous content of `/proc/irq/default_smp_affinity` is written to `/pro
If the intersection is an empty set, then just the non-isolated cores are written to `/proc/irq/default_smp_affinity`.
This behavior is the default if the parameter `default_irq_smp_affinity` is omitted.
`ignore`::
*Tuned* will not touch `/proc/irq/default_smp_affinity`.
*TuneD* will not touch `/proc/irq/default_smp_affinity`.
cpulist such as `1,3-4`::
The cpulist is unpacked and written directly to `/proc/irq/default_smp_affinity`.
--
@ -119,18 +119,18 @@ The cpulist is unpacked and written directly to `/proc/irq/default_smp_affinity`
`script`::
Executes an external script or binary when the profile is loaded or unloaded. You can choose an arbitrary executable.
+
IMPORTANT: The `script` plug-in is provided mainly for compatibility with earlier releases. Prefer other *Tuned* plug-ins if they cover the required functionality.
IMPORTANT: The `script` plug-in is provided mainly for compatibility with earlier releases. Prefer other *TuneD* plug-ins if they cover the required functionality.
+
*Tuned* calls the executable with one of the following arguments:
*TuneD* calls the executable with one of the following arguments:
+
--
** `start` when loading the profile
** `stop` when unloading the profile
--
+
You need to correctly implement the `stop` action in your executable and revert all settings that you changed during the `start` action. Otherwise, the roll-back step after changing your *Tuned* profile will not work.
You need to correctly implement the `stop` action in your executable and revert all settings that you changed during the `start` action. Otherwise, the roll-back step after changing your *TuneD* profile will not work.
+
Bash scripts can import the [filename]`/usr/lib/tuned/functions` Bash library and use the functions defined there. Use these functions only for functionality that is not natively provided by *Tuned*. If a function name starts with an underscore, such as `_wifi_set_power_level`, consider the function private and do not use it in your scripts, because it might change in the future.
Bash scripts can import the [filename]`/usr/lib/tuned/functions` Bash library and use the functions defined there. Use these functions only for functionality that is not natively provided by *TuneD*. If a function name starts with an underscore, such as `_wifi_set_power_level`, consider the function private and do not use it in your scripts, because it might change in the future.
+
Specify the path to the executable using the `script` parameter in the plug-in configuration.
+
@ -189,7 +189,7 @@ cmdline=[replaceable]_arg1_ [replaceable]_arg2_ ... [replaceable]_argN_
--
.Modifying the kernel command line
====
For example, to add the [option]`quiet` kernel option to a *Tuned* profile, include the following lines in the [filename]`tuned.conf` file:
For example, to add the [option]`quiet` kernel option to a *TuneD* profile, include the following lines in the [filename]`tuned.conf` file:
----
[bootloader]

6
doc/manual/modules/performance/ref_built-in-functions-available-in-tuned-profiles.adoc
View file

@ -1,7 +1,7 @@
[id="built-in-functions-available-in-tuned-profiles_{context}"]
= Built-in functions available in Tuned profiles
= Built-in functions available in TuneD profiles
The following built-in functions are available in all *Tuned* profiles:
The following built-in functions are available in all *TuneD* profiles:
`PROFILE_DIR`::
Returns the directory path where the profile and the `tuned.conf` file are located.
@ -25,7 +25,7 @@ Converts disk sectors to kilobytes.
Creates a string from all passed arguments and deletes both leading and trailing white space.
`virt_check`::
Checks whether *Tuned* is running inside a virtual machine (VM) or on bare metal:
Checks whether *TuneD* is running inside a virtual machine (VM) or on bare metal:
+
* Inside a VM, the function returns the first argument.
* On bare metal, the function returns the second argument, even in case of an error.

10
doc/manual/modules/performance/ref_tuned-profiles-distributed-with-rhel.adoc
View file

@ -1,16 +1,16 @@
[id="tuned-profiles-distributed-with-rhel_{context}"]
= Tuned profiles distributed with RHEL
= TuneD profiles distributed with RHEL
The following is a list of profiles that are installed with *Tuned* on {RHEL}.
The following is a list of profiles that are installed with *TuneD* on {RHEL}.
NOTE: There might be more product-specific or third-party *Tuned* profiles available. Such profiles are usually provided by separate RPM packages.
NOTE: There might be more product-specific or third-party *TuneD* profiles available. Such profiles are usually provided by separate RPM packages.
`balanced`::
The default power-saving profile. It is intended to be a compromise between performance and power consumption. It uses auto-scaling and auto-tuning whenever possible. The only drawback is the increased latency. In the current *Tuned* release, it enables the CPU, disk, audio, and video plugins, and activates the `conservative` CPU governor. The `radeon_powersave` option uses the `dpm-balanced` value if it is supported, otherwise it is set to `auto`.
The default power-saving profile. It is intended to be a compromise between performance and power consumption. It uses auto-scaling and auto-tuning whenever possible. The only drawback is the increased latency. In the current *TuneD* release, it enables the CPU, disk, audio, and video plugins, and activates the `conservative` CPU governor. The `radeon_powersave` option uses the `dpm-balanced` value if it is supported, otherwise it is set to `auto`.
`powersave`::
A profile for maximum power saving performance. It can throttle the performance in order to minimize the actual power consumption. In the current *Tuned* release it enables USB autosuspend, WiFi power saving, and Aggressive Link Power Management (ALPM) power savings for SATA host adapters. It also schedules multi-core power savings for systems with a low wakeup rate and activates the `ondemand` governor. It enables AC97 audio power saving or, depending on your system, HDA-Intel power savings with a 10 seconds timeout. If your system contains a supported Radeon graphics card with enabled KMS, the profile configures it to automatic power saving. On ASUS Eee PCs, a dynamic Super Hybrid Engine is enabled.
A profile for maximum power saving performance. It can throttle the performance in order to minimize the actual power consumption. In the current *TuneD* release it enables USB autosuspend, WiFi power saving, and Aggressive Link Power Management (ALPM) power savings for SATA host adapters. It also schedules multi-core power savings for systems with a low wakeup rate and activates the `ondemand` governor. It enables AC97 audio power saving or, depending on your system, HDA-Intel power savings with a 10 seconds timeout. If your system contains a supported Radeon graphics card with enabled KMS, the profile configures it to automatic power saving. On ASUS Eee PCs, a dynamic Super Hybrid Engine is enabled.
+
[NOTE]
--

4
experiments/powertop2tuned.py
View file

@ -261,7 +261,7 @@ class PowertopProfile:
return True
def generateTunedConf(self, profile, plugins):
print("Generating Tuned config file", os.path.join(self.output, "tuned.conf"))
print("Generating TuneD config file", os.path.join(self.output, "tuned.conf"))
f = codecs.open(os.path.join(self.output, "tuned.conf"), "w", "utf-8")
f.write(TUNED_CONF_PROLOG)
if profile is not None:
@ -316,7 +316,7 @@ class PowertopProfile:
return 0
if __name__ == "__main__":
parser = argparse.ArgumentParser(description='Creates Tuned profile from Powertop HTML output.')
parser = argparse.ArgumentParser(description='Creates TuneD profile from Powertop HTML output.')
parser.add_argument('profile', metavar='profile_name', type=str, nargs='?', help='Name for the profile to be written.')
parser.add_argument('-i', '--input', metavar='input_html', type=str, help='Path to Powertop HTML report. If not given, it is generated automatically.')
parser.add_argument('-o', '--output', metavar='output_directory', type=str, help='Directory where the profile will be written, default is /etc/tuned/profile_name directory.')

2
man/tuned-adm.8
View file

@ -19,7 +19,7 @@
.\" * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
.\" */
.\"
.TH TUNED_ADM "8" "30 Mar 2017" "Fedora Power Management SIG" "tuned"
.TH TUNED_ADM "8" "30 Mar 2017" "Fedora Power Management SIG" "TuneD"
.SH NAME
tuned\-adm - command line tool for switching between different tuning profiles
.SH SYNOPSIS

10
man/tuned-gui.8
View file

@ -18,15 +18,15 @@
.\" * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
.\" */
.\".
.TH "tuned-gui" "8" "22 Mar 2019" "Fedora Power Management SIG" "Tuned"
.TH "tuned-gui" "8" "22 Mar 2019" "Fedora Power Management SIG" "TuneD"
.SH NAME
tuned\-gui - graphical interface for configuration of Tuned
tuned\-gui - graphical interface for configuration of TuneD
.SH SYNOPSIS
\fBtuned\-gui\fP
.SH DESCRIPTION
\fBtuned-gui\fP is graphical interface for configuration of Tuned daemon. GUI
allows user to easily create, remove or update Tuned profiles and load those
profiles into Tuned. It is also possible to explore all available plugins and
\fBtuned-gui\fP is graphical interface for configuration of TuneD daemon. GUI
allows user to easily create, remove or update TuneD profiles and load those
profiles into TuneD. It is also possible to explore all available plugins and
information about them, like their description or help for their configuration
parameters.
.SH "TABS"

26
man/tuned-main.conf.5
View file

@ -1,16 +1,16 @@
.TH "tuned-main.conf" "5" "15 Oct 2013" "Jaroslav Škarvada" "tuned-main.conf file format description"
.SH NAME
tuned\-main.conf - Tuned global configuration file
tuned\-main.conf - TuneD global configuration file
.SH SYNOPSIS
.B /etc/tuned/tuned\-main.conf
.SH DESCRIPTION
This man page documents format of the Tuned global configuration file.
This man page documents format of the TuneD global configuration file.
The \fItuned\-main.conf\fR file uses the ini\-file format.
.TP
.BI daemon= BOOL
This defines whether Tuned will use daemon or not. It is boolean value.
This defines whether TuneD will use daemon or not. It is boolean value.
It can be \fBTrue\fR or \fB1\fR if the daemon is enabled and
\fBFalse\fR or \fB0\fR if disabled. It is not recommended to disable
daemon, because many functions will not work without daemon, e.g.
@ -28,11 +28,11 @@ to individually disable it in plugins. It is only applicable if
.TP
.BI sleep_interval= INT
Tuned daemon is periodically waken after \fIINT\fR seconds and checks
TuneD daemon is periodically waken after \fIINT\fR seconds and checks
for events. By default this is set to 1 second. If you have Python 2
interpreter with applied patch from Red Hat Bugzilla #917709 this
controls responsiveness time of Tuned to commands (i.e. if you
request profile switch, it may take up to 1 second until Tuned reacts).
controls responsiveness time of TuneD to commands (i.e. if you
request profile switch, it may take up to 1 second until TuneD reacts).
Increase this number for higher responsiveness times and more power
savings (due to lower number of wakeups). In case you have unpatched
Python 2 interpreter, this settings will have no visible effect,
@ -41,11 +41,11 @@ applicable if \fBdaemon\fR is enabled.
.TP
.BI update_interval= INT
Update interval for dynamic tuning (in seconds). Tuned daemon is periodically
Update interval for dynamic tuning (in seconds). TuneD daemon is periodically
waken after \fIINT\fR seconds, updates its monitors, calculates new tuning
parameters for enabled plugins and applies the changes. Plugins that have
disabled dynamic tuning are not processed. By default the \fIINT\fR is set
to 10 seconds. Tuned daemon doesn't periodically wake if dynamic tuning is
to 10 seconds. TuneD daemon doesn't periodically wake if dynamic tuning is
globally disabled (see \fBdynamic_tuning\fR) or this setting set to 0.
This must be multiple of \fBsleep_interval\fR. It is only applicable if
\fBdaemon\fR is enabled.
@ -55,26 +55,26 @@ This must be multiple of \fBsleep_interval\fR. It is only applicable if
This controls whether recommend functionality will be enabled or not. It is
boolean value. It can be \fBTrue\fR or \fB1\fR if the recommend command is
enabled and \fBFalse\fR or \fB0\fR if disabled. If disabled \fBrecommend\fR
command will be not available in CLI, tuned will not parse \fIrecommend.conf\fR
command will be not available in CLI, TuneD will not parse \fIrecommend.conf\fR
and will return one hardcoded profile (by default \fBbalanced\fR). It is only
applicable if \fBdaemon\fR is enabled. By default it's set to \fBTrue\fR.
.TP
.BI reapply_sysctl= BOOL
This controls whether to reapply sysctl settings from \fI/run/sysctl.d/*.conf\fR,
\fI/etc/sysctl.d/*.conf\fR and \fI/etc/sysctl.conf\fR after Tuned sysctl
\fI/etc/sysctl.d/*.conf\fR and \fI/etc/sysctl.conf\fR after TuneD sysctl
settings are applied. These are locations supported by \fBsysctl --system\fR,
excluding those that contain sysctl configuration files provided by system packages.
So if \fBreapply_sysctl\fR is set to \fBTrue\fR or \fB1\fR, Tuned sysctl settings
So if \fBreapply_sysctl\fR is set to \fBTrue\fR or \fB1\fR, TuneD sysctl settings
will not override user-provided system sysctl settings. If set to \fBFalse\fR or
\fB0\fR, Tuned sysctl settings will override system sysctl settings. By default
\fB0\fR, TuneD sysctl settings will override system sysctl settings. By default
it's set to \fBTrue\fR.
.TP
.BI default_instance_priority= INT
Default instance (unit) priority. By default it's \fB0\fR. Each unit has a
priority which is by default preset to the \fIINT\fR. It can be overridden
in the Tuned profile by the \fBpriority\fR option. Tuned units are processed
in the TuneD profile by the \fBpriority\fR option. TuneD units are processed
in order defined by their priorities, i.e. unit with the lowest number is
processed as the first.

2
man/tuned-profiles-atomic.7
View file

@ -18,7 +18,7 @@
.\" * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
.\" */
.\"
.TH TUNED_PROFILES_ATOMIC "7" "30 Mar 2017" "Fedora Power Management SIG" "tuned"
.TH TUNED_PROFILES_ATOMIC "7" "30 Mar 2017" "Fedora Power Management SIG" "TuneD"
.SH NAME
tuned\-profiles\-atomic - description of profiles provided for the Project Atomic

12
man/tuned-profiles-compat.7
View file

@ -19,7 +19,7 @@
.\" * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
.\" */
.\"
.TH TUNED_PROFILES_COMPAT "7" "30 Mar 2017" "Fedora Power Management SIG" "tuned"
.TH TUNED_PROFILES_COMPAT "7" "30 Mar 2017" "Fedora Power Management SIG" "TuneD"
.SH NAME
tuned\-profiles\-compat - description of profiles provided for backward compatibility
@ -27,7 +27,7 @@ tuned\-profiles\-compat - description of profiles provided for backward compatib
These profiles are provided for backward compatibility with the tuned-1x.
They are no longer maintained and may be dropped anytime in the future.
It's not recommended to use them for purposes other than backward compatibility.
Some of them are only aliases to base tuned profiles. Please do not use the compat
Some of them are only aliases to base TuneD profiles. Please do not use the compat
profiles on new installations and rather use profiles from base tuned package or
other tuned subpackages.
@ -37,23 +37,23 @@ The following profiles are considered compatibility profiles:
.TP
.BI "default"
It is the lowest of the available profiles in regard to power saving and only
enables CPU and disk plugins of tuned.
enables CPU and disk plugins of TuneD.
.TP
.BI "desktop\-powersave"
A power saving profile directed at desktop systems. Enables ALPM power saving
for SATA host adapters as well as the CPU, ethernet and disk plugins of tuned.
for SATA host adapters as well as the CPU, ethernet and disk plugins of TuneD.
.TP
.BI server\-powersave
A power saving profile directed at server systems. Enables ALPM power saving
for SATA host adapters, and activates the CPU and disk plugins of tuned.
for SATA host adapters, and activates the CPU and disk plugins of TuneD.
.TP
.BI laptop\-ac\-powersave
Medium power saving profile directed at laptops running on AC. Enables ALPM
power saving for SATA host adapters, WiFi power saving as well as CPU,
ethernet and disk plugins of tuned.
ethernet and disk plugins of TuneD.
.TP
.BI laptop\-battery\-powersave

2
man/tuned-profiles-cpu-partitioning.7
View file

@ -18,7 +18,7 @@
.\" * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
.\" */
.\"
.TH TUNED_PROFILES_CPU_PARTITIONING "7" "22 Feb 2018" "tuned"
.TH TUNED_PROFILES_CPU_PARTITIONING "7" "22 Feb 2018" "TuneD"
.SH NAME
tuned\-profiles\-cpu\-partitioning - Partition CPUs into isolated and housekeeping.

2
man/tuned-profiles-mssql.7
View file

@ -18,7 +18,7 @@
.\" * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
.\" */
.\"
.TH TUNED_PROFILES_MSSQL "7" "05 Jun 2018" "Red Hat, Inc." "tuned"
.TH TUNED_PROFILES_MSSQL "7" "05 Jun 2018" "Red Hat, Inc." "TuneD"
.SH NAME
tuned\-profiles\-mssql - description of profile provided for the MS SQL Server

2
man/tuned-profiles-nfv-guest.7
View file

@ -18,7 +18,7 @@
.\" * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
.\" */
.\"
.TH TUNED_PROFILES_NFV_GUEST "7" "30 Mar 2017" "Fedora Power Management SIG" "tuned"
.TH TUNED_PROFILES_NFV_GUEST "7" "30 Mar 2017" "Fedora Power Management SIG" "TuneD"
.SH NAME
tuned\-profiles\-nfv\-guest - description of profile provided for the NFV guest

2
man/tuned-profiles-nfv-host.7
View file

@ -18,7 +18,7 @@
.\" * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
.\" */
.\"
.TH TUNED_PROFILES_NFV_HOST "7" "30 Mar 2017" "Fedora Power Management SIG" "tuned"
.TH TUNED_PROFILES_NFV_HOST "7" "30 Mar 2017" "Fedora Power Management SIG" "TuneD"
.SH NAME
tuned\-profiles\-nfv\-host - description of profile provided for the NFV host

2
man/tuned-profiles-oracle.7
View file

@ -18,7 +18,7 @@
.\" * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
.\" */
.\"
.TH TUNED_PROFILES_ORACLE "7" "30 Mar 2017" "Fedora Power Management SIG" "tuned"
.TH TUNED_PROFILES_ORACLE "7" "30 Mar 2017" "Fedora Power Management SIG" "TuneD"
.SH NAME
tuned\-profiles\-oracle - description of profiles provided for the Oracle

2
man/tuned-profiles-postgresql.7
View file

@ -20,7 +20,7 @@
.\" * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
.\" */
.\"
.TH TUNED_PROFILES_POSTGRESQL "7" "29 Jul 2020" "Fedora Power Management SIG" "tuned"
.TH TUNED_PROFILES_POSTGRESQL "7" "29 Jul 2020" "Fedora Power Management SIG" "TuneD"
.SH NAME
tuned\-profiles\-postgresql - description of profiles provided for PostgreSQL Server

2
man/tuned-profiles-realtime.7
View file

@ -18,7 +18,7 @@
.\" * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
.\" */
.\"
.TH TUNED_PROFILES_REALTIME "7" "30 Mar 2017" "Fedora Power Management SIG" "tuned"
.TH TUNED_PROFILES_REALTIME "7" "30 Mar 2017" "Fedora Power Management SIG" "TuneD"
.SH NAME
tuned\-profiles\-realtime - description of profiles provided for the realtime

2
man/tuned-profiles-sap-hana.7
View file

@ -18,7 +18,7 @@
.\" * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
.\" */
.\"
.TH TUNED_PROFILES_SAP_HANA "7" "30 Mar 2017" "Fedora Power Management SIG" "tuned"
.TH TUNED_PROFILES_SAP_HANA "7" "30 Mar 2017" "Fedora Power Management SIG" "TuneD"
.SH NAME
tuned\-profiles\-sap\-hana - description of profiles provided for the SAP HANA

2
man/tuned-profiles-sap.7
View file

@ -18,7 +18,7 @@
.\" * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
.\" */
.\"
.TH TUNED_PROFILES_SAP "7" "30 Mar 2017" "Fedora Power Management SIG" "tuned"
.TH TUNED_PROFILES_SAP "7" "30 Mar 2017" "Fedora Power Management SIG" "TuneD"
.SH NAME
tuned\-profiles\-sap - description of profiles provided for the SAP NetWeaver

2
man/tuned-profiles-spectrumscale-ece.7
View file

@ -18,7 +18,7 @@
.\" * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
.\" */
.\"
.TH TUNED_PROFILES_SPECTRUMSCALE_ECE "7" "22 Apr 2020" "Fedora Power Management SIG" "tuned"
.TH TUNED_PROFILES_SPECTRUMSCALE_ECE "7" "22 Apr 2020" "Fedora Power Management SIG" "TuneD"
.SH NAME
tuned\-profiles\-spectrumscale-ece - description of profiles provided for Spectrum Scale Erasure Code Edition

12
man/tuned-profiles.7
View file

@ -19,9 +19,9 @@
.\" * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
.\" */
.\"
.TH TUNED_PROFILES "7" "30 Mar 2017" "Fedora Power Management SIG" "tuned"
.TH TUNED_PROFILES "7" "30 Mar 2017" "Fedora Power Management SIG" "TuneD"
.SH NAME
tuned\-profiles - description of basic tuned profiles
tuned\-profiles - description of basic TuneD profiles
.SH DESCRIPTION
These are the base profiles which are mostly shipped in the base tuned
@ -33,14 +33,14 @@ purpose of the profile by its name or you can see full description below.
The profiles are stored in subdirectories below \fI/usr/lib/tuned\fP. If you
need to customize the profiles, you can copy them to \fI/etc/tuned\fP and modify
them as you need. When loading profiles with the same name, the /etc/tuned takes
precedence. In such case you will not lose your customized profiles between
tuned updates.
precedence. In such case you will not lose your customized profiles between
TuneD updates.
The power saving profiles contain settings that are typically not enabled by
default as they will noticeably impact the latency/performance of your system
as opposed to the power saving mechanisms that are enabled by default. On the
other hand the performance profiles disable the additional power saving
mechanisms of tuned as they would negatively impact throughput or latency.
mechanisms of TuneD as they would negatively impact throughput or latency.
.SH PROFILES
At the moment we're providing the following pre\-defined profiles:
@ -48,7 +48,7 @@ At the moment we're providing the following pre\-defined profiles:
.TP
.BI "balanced"
It is the default profile. It provides balanced power saving and performance.
At the moment it enables CPU and disk plugins of tuned and it makes sure the
At the moment it enables CPU and disk plugins of TuneD and it makes sure the
conservative governor is active (if supported by the current cpufreq driver).
It enables ALPM power saving for SATA host adapters and sets the link power
management policy to medium_power. It also sets the CPU energy performance

2
man/tuned.8
View file

@ -21,7 +21,7 @@
.\".
.TH "tuned" "8" "28 Mar 2012" "Fedora Power Management SIG" "Adaptive system tuning daemon"
.SH NAME
tuned - dynamic adaptive system tuning daemon
TuneD - dynamic adaptive system tuning daemon
.SH SYNOPSIS
\fBtuned\fP [\fIoptions\fP]
.SH DESCRIPTION

6
man/tuned.conf.5
View file

@ -1,8 +1,8 @@
.TH "tuned.conf" "5" "13 Mar 2012" "Jan Kaluža" "tuned.conf file format description"
.SH NAME
tuned.conf - Tuned profile definition
tuned.conf - TuneD profile definition
.SH DESCRIPTION
This man page documents format of Tuned 2.0 profile definition files.
This man page documents format of TuneD 2.0 profile definition files.
The profile definition is stored in /etc/tuned/<profile_name>/tuned.conf or in
/usr/lib/tuned/<profile_name>/tuned.conf file where the /etc/tuned/ directory has
higher priority.
@ -32,7 +32,7 @@ type=
Plugin type. Currently there are following upstream plugins: audio, bootloader, cpu, disk,
eeepc_she, modules, mounts, net, script, scsi_host, selinux, scheduler, sysctl,
sysfs, systemd, usb, video, vm. This list may be incomplete. If you installed
tuned through RPM you can list upstream plugins by the following command:
TuneD through RPM you can list upstream plugins by the following command:
.B rpm -ql tuned | grep 'plugins/plugin_.*.py$'
Check the plugins directory returned by this command to see all plugins (e.g. plugins
provided by 3rd party packages).

12
modules.conf
View file

@ -1,11 +1,11 @@
# This file specifies additional parameters to kernel modules added by Tuned.
# Its content is set by the Tuned modules plugin.
# This file specifies additional parameters to kernel modules added by TuneD.
# Its content is set by the TuneD modules plugin.
#
# Please do not edit this file. Content of this file can be overwritten by
# switch of Tuned profile.
# switch of TuneD profile.
#
# If you need to add kernel module parameter which should be handled by Tuned,
# create Tuned profile containing the following:
# If you need to add kernel module parameter which should be handled by TuneD,
# create TuneD profile containing the following:
#
# [modules]
# MODULE_NAME = MODULE_PARAMETERS
@ -16,7 +16,7 @@
#
# and reboot or reload the module
#
# Tuned tries to automatically reload the module if specified the following
# TuneD tries to automatically reload the module if specified the following
# way:
#
# [modules]

2
recommend.conf
View file

@ -1,4 +1,4 @@
# Tuned rules for recommend_profile.
# TuneD rules for recommend_profile.
#
# Syntax:
# [PROFILE1]

4
tests/beakerlib/Tuned-takes-too-long-to-reload-start-when-ulimit/main.fmf
View file

@ -1,9 +1,9 @@
component: tuned
contact: Robin Hack <rhack@redhat.com>
description: |
Bug summary: Tuned takes too long to reload/start when "ulimit -n" is high.
Bug summary: TuneD takes too long to reload/start when "ulimit -n" is high.
Bugzilla link: https://bugzilla.redhat.com/show_bug.cgi?id=1663412
duration: 20m
relevancy: |
distro = rhel-4, rhel-5, rhel-6: False
summary: Test for BZ#1663412 (Tuned takes too long to reload/start when \"ulimit)
summary: Test for BZ#1663412 (TuneD takes too long to reload/start when \"ulimit)

2
tests/beakerlib/Tuned-takes-too-long-to-reload-start-when-ulimit/runtest.sh
View file

@ -3,7 +3,7 @@
# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
#
# runtest.sh of /CoreOS/tuned/Regression/Tuned-takes-too-long-to-reload-start-when-ulimit
# Description: Test for BZ#1663412 (Tuned takes too long to reload/start when "ulimit)
# Description: Test for BZ#1663412 (TuneD takes too long to reload/start when "ulimit)
# Author: Robin Hack <rhack@redhat.com>
#
# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

28
tests/beakerlib/bz1798183-RFE-support-post-loaded-profile/runtest.sh
View file

@ -94,7 +94,7 @@ rlJournalStart
rlPhaseStartTest "Check that settings from the post-loaded profile are applied"
rlRun "tuned-adm profile parent"
rlRun "echo post > $POST_LOADED_PROFILE"
# Restart Tuned so that the post-loaded profile gets applied
# Restart TuneD so that the post-loaded profile gets applied
rlRun "rlServiceStart tuned"
rlAssertEquals "Check that swappiness is set correctly" \
"$(sysctl -n $SWAPPINESS)" 20
@ -112,7 +112,7 @@ rlJournalStart
pid=$!
# Give the wait_for_signal script a chance to connect to the bus
sleep 1
rlRun "kill -HUP '$(< $PID_FILE)'" 0 "Send HUP to Tuned"
rlRun "kill -HUP '$(< $PID_FILE)'" 0 "Send HUP to TuneD"
rlRun "wait $pid"
rlAssertEquals "Check that swappiness is set correctly" \
"$(sysctl -n $SWAPPINESS)" 30
@ -120,10 +120,10 @@ rlJournalStart
"$(sysctl -n $DIRTY_RATIO)" 7
rlPhaseEnd
rlPhaseStartTest "Check that 'tuned-adm profile' does not cause Tuned to touch the post-loaded profile"
rlPhaseStartTest "Check that 'tuned-adm profile' does not cause TuneD to touch the post-loaded profile"
rlRun "tuned-adm profile parent"
rlRun "echo post > $POST_LOADED_PROFILE"
# Restart Tuned so that the post-loaded profile gets applied
# Restart TuneD so that the post-loaded profile gets applied
rlRun "rlServiceStart tuned"
# Change the active profile. After this, the profile 'post' must remain applied.
rlRun "tuned-adm profile parent2"
@ -136,7 +136,7 @@ rlJournalStart
rlPhaseStartTest "Check that settings from the post-loaded profile take precedence"
rlRun "tuned-adm profile parent"
rlRun "echo conflicting > $POST_LOADED_PROFILE"
# Restart Tuned so that the post-loaded profile gets applied
# Restart TuneD so that the post-loaded profile gets applied
rlRun "rlServiceStart tuned"
rlAssertEquals "Check that swappiness is set correctly" \
"$(sysctl -n $SWAPPINESS)" 10
@ -145,15 +145,15 @@ rlJournalStart
rlPhaseStartTest "Check that conflicts in the post-loaded profile do not cause verification to fail"
rlRun "tuned-adm profile parent"
rlRun "echo conflicting > $POST_LOADED_PROFILE"
# Restart Tuned so that the post-loaded profile gets applied
# Restart TuneD so that the post-loaded profile gets applied
rlRun "rlServiceStart tuned"
rlRun "tuned-adm verify"
rlPhaseEnd
rlPhaseStartTest "Check that 'tuned-adm off' causes Tuned to clear the post-loaded profile"
rlPhaseStartTest "Check that 'tuned-adm off' causes TuneD to clear the post-loaded profile"
rlRun "tuned-adm profile parent"
rlRun "echo post > $POST_LOADED_PROFILE"
# Restart Tuned so that the post-loaded profile gets applied
# Restart TuneD so that the post-loaded profile gets applied
rlRun "rlServiceStart tuned"
rlRun "tuned-adm off"
rlAssertEquals "Check the output of tuned-adm active" \
@ -169,7 +169,7 @@ rlJournalStart
rlRun "> $ACTIVE_PROFILE"
rlRun "echo manual > $PROFILE_MODE"
rlRun "echo post > $POST_LOADED_PROFILE"
# Restart Tuned so that the post-loaded profile gets applied
# Restart TuneD so that the post-loaded profile gets applied
rlRun "rlServiceStart tuned"
rlAssertEquals "Check the output of tuned-adm active" \
"$(tuned-adm active)" \
@ -181,7 +181,7 @@ rlJournalStart
rlPhaseStartTest "Check that the post-loaded profile is listed among active profiles by 'tuned-adm active'"
rlRun "tuned-adm profile parent"
rlRun "echo post > $POST_LOADED_PROFILE"
# Restart Tuned so that the post-loaded profile gets applied
# Restart TuneD so that the post-loaded profile gets applied
rlRun "rlServiceStart tuned"
rlAssertEquals "Check the output of tuned-adm active" \
"$(tuned-adm active | grep 'Current active profile')" \
@ -201,8 +201,8 @@ rlJournalStart
rlAssertEquals "Check the output of tuned-adm active" \
"$(tuned-adm active | grep 'Current active profile')" \
"Current active profile: parent post"
rlRun "kill '$(< $PID_FILE)'" 0 "Kill Tuned"
rlRun "wait_for_tuned_stop 15" 0 "Wait for Tuned to exit"
rlRun "kill '$(< $PID_FILE)'" 0 "Kill TuneD"
rlRun "wait_for_tuned_stop 15" 0 "Wait for TuneD to exit"
rlPhaseEnd
rlPhaseStartTest "Check that the DBus signal 'profile_changed' contains only the active_profile"
@ -228,7 +228,7 @@ rlJournalStart
"parent"
rlPhaseEnd
rlPhaseStartTest "Check that 'tuned-adm profile' does not cause Tuned to reload the post-loaded profile name from disk"
rlPhaseStartTest "Check that 'tuned-adm profile' does not cause TuneD to reload the post-loaded profile name from disk"
rlRun "tuned-adm profile parent"
rlRun "echo post > $POST_LOADED_PROFILE"
rlRun "rlServiceStart tuned"
@ -258,7 +258,7 @@ rlJournalStart
rlPhaseStartTest "Check that variables are shared among the active_profile and the post-loaded profile"
rlRun "tuned-adm profile parent-vars"
rlRun "echo post-vars > $POST_LOADED_PROFILE"
# Restart Tuned so that the post-loaded profile gets applied
# Restart TuneD so that the post-loaded profile gets applied
rlRun "rlServiceStart tuned"
rlAssertEquals "Check that swappiness is set correctly" \
"$(sysctl -n $SWAPPINESS)" 12

4
tests/beakerlib/error-messages/main.fmf
View file

@ -1,9 +1,9 @@
component: tuned
contact: Robin Hack <rhack@redhat.com>
description: |
Bug summary: Tuned logs error message if '/sys/class/scsi_host/host*/link_power_management_policy' file does not exists.
Bug summary: TuneD logs error message if '/sys/class/scsi_host/host*/link_power_management_policy' file does not exists.
Bugzilla link: https://bugzilla.redhat.com/show_bug.cgi?id=1416712
duration: 5m
relevancy: |
distro = rhel-4, rhel-5: False
summary: Test for BZ#1416712 (Tuned logs error message if)
summary: Test for BZ#1416712 (TuneD logs error message if)

2
tests/beakerlib/error-messages/runtest.sh
View file

@ -3,7 +3,7 @@
# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
#
# runtest.sh of /CoreOS/tuned/Regression/bz1416712-Tuned-logs-error-message-if
# Description: Test for BZ#1416712 (Tuned logs error message if)
# Description: Test for BZ#1416712 (TuneD logs error message if)
# Author: Tereza Cerna <tcerna@redhat.com>
#
# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

2
tuned-gui.desktop
View file

@ -1,7 +1,7 @@
[Desktop Entry]
Name=tuned-gui
GenericName=tuned
Comment=GTK GUI that can control Tuned daemon and provides simple profile editor
Comment=GTK GUI that can control TuneD daemon and provides simple profile editor
Exec=/usr/sbin/tuned-gui
Icon=tuned
Terminal=false

8
tuned-gui.glade
View file

@ -5,7 +5,7 @@
<object class="GtkAboutDialog" id="aboutdialog1">
<property name="can_focus">False</property>
<property name="type_hint">dialog</property>
<property name="program_name">Tuned Manager</property>
<property name="program_name">TuneD Manager</property>
<property name="logo_icon_name">image-missing</property>
<child>
<placeholder/>
@ -300,7 +300,7 @@
</object>
<object class="GtkWindow" id="mainWindow">
<property name="can_focus">False</property>
<property name="title" translatable="yes">Tuned Manager</property>
<property name="title" translatable="yes">TuneD Manager</property>
<signal name="destroy" handler="gtk_main_quit" swapped="no"/>
<child>
<placeholder/>
@ -398,7 +398,7 @@
<property name="can_focus">False</property>
<property name="halign">end</property>
<property name="hexpand">True</property>
<property name="label" translatable="yes">Tuned On Startup</property>
<property name="label" translatable="yes">TuneD On Startup</property>
<property name="ellipsize">end</property>
<property name="angle">0.029999999999999999</property>
<property name="xalign">0</property>
@ -448,7 +448,7 @@
<property name="can_focus">False</property>
<property name="halign">end</property>
<property name="hexpand">True</property>
<property name="label" translatable="yes">Start Tuned Daemon</property>
<property name="label" translatable="yes">Start TuneD Daemon</property>
<property name="ellipsize">end</property>
<property name="xalign">0</property>
</object>

8
tuned-gui.py
View file

@ -80,7 +80,7 @@ AUTHORS = [
class Base(object):
"""
GUI class for program Tuned.
GUI class for program TuneD.
"""
is_admin = False
@ -102,8 +102,8 @@ class Base(object):
self._gobj('tunedDaemonExceptionDialog').hide()
return True
else:
self.error_dialog('Tuned is shutting down.',
'Reason: missing communication with Tuned daemon.'
self.error_dialog('TuneD is shutting down.',
'Reason: missing communication with TuneD daemon.'
)
return False
return True
@ -706,7 +706,7 @@ class Base(object):
self.is_tuned_connection_ok()
else:
self._su_execute(['service', 'tuned', 'stop'])
self.error_dialog('Tuned Daemon is turned off',
self.error_dialog('TuneD Daemon is turned off',
'Support of tuned is not running.')
elif switch == self._gobj('switchTunedStartupStartStop'):

2
tuned-main.conf
View file

@ -24,7 +24,7 @@ recommend_command = 1
# Whether to reapply sysctl from /run/sysctl.d/, /etc/sysctl.d/ and
# /etc/sysctl.conf. If enabled, these sysctls will be re-appliead
# after Tuned sysctls are applied, i.e. Tuned sysctls will not
# after TuneD sysctls are applied, i.e. TuneD sysctls will not
# override user-provided system sysctls.
reapply_sysctl = 1

12
tuned/admin/admin.py
View file

@ -274,7 +274,7 @@ class Admin(object):
print(log_msgs, end = "", file = sys.stderr)
sys.stderr.flush()
except TunedAdminDBusException as e:
self._error("Error: Failed to stop log capture. Restart the Tuned daemon to prevent a memory leak.")
self._error("Error: Failed to stop log capture. Restart the TuneD daemon to prevent a memory leak.")
def _action_dbus_profile(self, profiles):
if len(profiles) == 0:
@ -300,9 +300,9 @@ class Admin(object):
print("Trying to (re)start tuned...")
(ret, msg) = self._cmd.execute(["service", "tuned", "restart"])
if ret == 0:
print("Tuned (re)started, changes applied.")
print("TuneD (re)started, changes applied.")
else:
print("Tuned (re)start failed, you need to (re)start tuned by hand for changes to apply.")
print("TuneD (re)start failed, you need to (re)start TuneD by hand for changes to apply.")
def _set_profile(self, profile_name, manual):
if profile_name in self._profiles_locator.get_known_names():
@ -363,12 +363,12 @@ class Admin(object):
print("Verfication succeeded, current system settings match the preset profile.")
else:
print("Verification failed, current system settings differ from the preset profile.")
print("You can mostly fix this by restarting the Tuned daemon, e.g.:")
print("You can mostly fix this by restarting the TuneD daemon, e.g.:")
print(" systemctl restart tuned")
print("or")
print(" service tuned restart")
print("Sometimes (if some plugins like bootloader are used) a reboot may be required.")
print("See tuned log file ('%s') for details." % consts.LOG_FILE)
print("See TuneD log file ('%s') for details." % consts.LOG_FILE)
return self._controller.exit(ret)
def _action_verify_profile(self, ignore_missing):
@ -390,7 +390,7 @@ class Admin(object):
return False
def _action_dbus_list(self, list_choice="profiles", verbose=False):
"""Print accessible profiles or plugins got from tuned dbus api
"""Print accessible profiles or plugins got from TuneD dbus api
Keyword arguments:
list_choice -- argument from command line deciding what will be listed

4
tuned/admin/dbus_controller.py
View file

@ -31,7 +31,7 @@ class DBusController(object):
self._proxy = bus.get_object(self._bus_name, self._object_name)
self._interface = dbus.Interface(self._proxy, dbus_interface = self._interface_name)
except dbus.exceptions.DBusException:
raise TunedAdminDBusException("Cannot talk to Tuned daemon via DBus. Is Tuned daemon running?")
raise TunedAdminDBusException("Cannot talk to TuneD daemon via DBus. Is TuneD daemon running?")
def _idle(self):
if self._action is not None:
@ -78,7 +78,7 @@ class DBusController(object):
method = self._interface.get_dbus_method(method_name)
return method(*args, timeout=40)
except dbus.exceptions.DBusException as dbus_exception:
err_str = "DBus call to Tuned daemon failed"
err_str = "DBus call to TuneD daemon failed"
if self._debug:
err_str += " (%s)" % str(dbus_exception)
raise TunedAdminDBusException(err_str)

2
tuned/daemon/controller.py
View file

@ -138,7 +138,7 @@ class Controller(tuned.exports.interfaces.ExportableInterface):
try:
self._daemon.reload_profile_config()
except TunedException as e:
log.error("Failed to reload Tuned: %s" % e)
log.error("Failed to reload TuneD: %s" % e)
return False
return self.start()

12
tuned/daemon/daemon.py
View file

@ -213,7 +213,7 @@ class Daemon(object):
# poll, otherwise the python will not have chance to update events / locks (due to GIL)
# and e.g. DBus control will not work. The polling interval of 1 seconds (which is
# the default) is still much better than 50 ms polling with unpatched interpreter.
# For more details see tuned rhbz#917587.
# For more details see TuneD rhbz#917587.
_sleep_cnt = self._sleep_cycles
while not self._cmd.wait(self._terminate, self._sleep_interval):
if self._dynamic_tuning:
@ -238,18 +238,18 @@ class Daemon(object):
full_rollback = True
else:
# with systemd it detects system shutdown and in such case it doesn't perform
# full cleanup, if not shutting down it means that Tuned was explicitly
# full cleanup, if not shutting down it means that TuneD was explicitly
# stopped by user and in such case do full cleanup, without systemd never
# do full cleanup
full_rollback = False
if self._full_rollback_required():
if self._daemon:
log.info("terminating Tuned, rolling back all changes")
log.info("terminating TuneD, rolling back all changes")
full_rollback = True
else:
log.info("terminating Tuned in one-shot mode")
log.info("terminating TuneD in one-shot mode")
else:
log.info("terminating Tuned due to system shutdown / reboot")
log.info("terminating TuneD due to system shutdown / reboot")
if self._daemon:
self._unit_manager.stop_tuning(full_rollback)
self._unit_manager.destroy_all()
@ -334,7 +334,7 @@ class Daemon(object):
def verify_profile(self, ignore_missing):
if not self.is_running():
log.error("tuned is not running")
log.error("TuneD is not running")
return False
if self._profile is None:

6
tuned/gtk/gui_plugin_loader.py
View file

@ -88,14 +88,14 @@ class GuiPluginLoader():
configspec=global_config_spec,
raise_errors = True, file_error = True, list_values = False, interpolation = False)
except IOError as e:
raise TunedException("Global tuned configuration file '%s' not found."
raise TunedException("Global TuneD configuration file '%s' not found."
% file_name)
except ConfigObj.ConfigObjError as e:
raise TunedException("Error parsing global tuned configuration file '%s'."
raise TunedException("Error parsing global TuneD configuration file '%s'."
% file_name)
vdt = Validator()
if not config.validate(vdt, copy=True):
raise TunedException("Global tuned configuration file '%s' is not valid."
raise TunedException("Global TuneD configuration file '%s' is not valid."
% file_name)
return config

2
tuned/hardware/inventory.py
View file

@ -29,7 +29,7 @@ class Inventory(object):
self._udev_monitor.set_receive_buffer_size(buffer_size)
except EnvironmentError:
log.warn("cannot set udev monitor receive buffer size, we are probably running inside " +
"container or with limited capabilites, Tuned functionality may be limited")
"container or with limited capabilites, TuneD functionality may be limited")
if monitor_observer_factory is None:
monitor_observer_factory = _MonitorObserverFactory()

2
tuned/logs.py
View file

@ -86,7 +86,7 @@ def get():
assert False
class TunedLogger(logging.getLoggerClass()):
"""Custom tuned daemon logger class."""
"""Custom TuneD daemon logger class."""
_formatter = logging.Formatter("%(asctime)s %(levelname)-8s %(name)s: %(message)s")
_console_handler = None
_file_handler = None

6
tuned/plugins/plugin_bootloader.py
View file

@ -114,7 +114,7 @@ class BootloaderPlugin(base.Plugin):
def _instance_unapply_static(self, instance, full_rollback = False):
if full_rollback:
log.info("removing grub2 tuning previously added by Tuned")
log.info("removing grub2 tuning previously added by TuneD")
self._remove_grub2_tuning()
self._update_grubenv({"tuned_params" : "", "tuned_initrd" : ""})
@ -137,9 +137,9 @@ class BootloaderPlugin(base.Plugin):
d2 = {"linux" : consts.GRUB2_TUNED_VAR, "initrd" : consts.GRUB2_TUNED_INITRD_VAR}
for i in d2:
# add tuned parameters to all kernels
# add TuneD parameters to all kernels
grub2_cfg = re.sub(r"^(\s*" + i + r"(16|efi)?\s+.*)$", r"\1 $" + d2[i], grub2_cfg, flags = re.MULTILINE)
# remove tuned parameters from rescue kernels
# remove TuneD parameters from rescue kernels
grub2_cfg = re.sub(r"^(\s*" + i + r"(?:16|efi)?\s+\S+rescue.*)\$" + d2[i] + r" *(.*)$", r"\1\2", grub2_cfg, flags = re.MULTILINE)
# fix whitespaces in rescue kernels
grub2_cfg = re.sub(r"^(\s*" + i + r"(?:16|efi)?\s+\S+rescue.*) +$", r"\1", grub2_cfg, flags = re.MULTILINE)

4
tuned/plugins/plugin_systemd.py
View file

@ -97,11 +97,11 @@ class SystemdPlugin(base.Plugin):
def _instance_unapply_static(self, instance, full_rollback = False):
if full_rollback:
log.info("removing '%s' systemd tuning previously added by Tuned" % consts.SYSTEMD_CPUAFFINITY_VAR)
log.info("removing '%s' systemd tuning previously added by TuneD" % consts.SYSTEMD_CPUAFFINITY_VAR)
self._remove_systemd_tuning()
log.console("you may need to manualy run 'dracut -f' to update the systemd configuration in initrd image")
# convert cpulist from systemd syntax to Tuned syntax and unpack it
# convert cpulist from systemd syntax to TuneD syntax and unpack it
def _cpulist_convert_unpack(self, cpulist):
if cpulist is None:
return ""

2
tuned/units/manager.py
View file

@ -165,7 +165,7 @@ class Manager(object):
# back is needed, e.g. for bootloader plugin we need e.g grub.cfg
# tuning to persist across reboots and restarts of the daemon, so in
# this case the full_rollback is usually set to False, but we also
# need to clean it all up when Tuned is disabled or the profile is
# need to clean it all up when TuneD is disabled or the profile is
# changed. In this case the full_rollback is set to True. In practice
# it means to remove all temporal or helper files, unpatch third
# party config files, etc.

6
tuned/utils/global_config.py
View file

@ -30,12 +30,12 @@ class GlobalConfig():
self._cfg = ConfigObj(file_name, configspec = self.global_config_spec, raise_errors = True, \
file_error = True, list_values = False, interpolation = False)
except IOError as e:
raise TunedException("Global tuned configuration file '%s' not found." % file_name)
raise TunedException("Global TuneD configuration file '%s' not found." % file_name)
except ConfigObjError as e:
raise TunedException("Error parsing global tuned configuration file '%s'." % file_name)
raise TunedException("Error parsing global TuneD configuration file '%s'." % file_name)
vdt = Validator()
if (not self._cfg.validate(vdt, copy=True)):
raise TunedException("Global tuned configuration file '%s' is not valid." % file_name)
raise TunedException("Global TuneD configuration file '%s' is not valid." % file_name)
def get(self, key, default = None):
return self._cfg.get(key, default)