tuned.conf(5)

💖 tuned.conf(5) — the TuneD profile glow-up guide 💖

okay bestie, sit down, hydrate, and let me tell you about tuned.conf — the file format that defines a TuneD profile. This is the tuned.conf(5) manual page, and yes, we're gonna read it together, because it's actually kind of iconic.

---

✨ DESCRIPTION ✨

This page documents the format of TuneD 2.0 profile definition files. fr fr, that's the whole assignment.

Your profile definition lives in one of two places:

• /etc/tuned/profiles/<profile_name>/tuned.conf
• /usr/lib/tuned/profiles/<profile_name>/tuned.conf

and here's the tea: the /etc/tuned/profiles/ directory has higher priority. So if both exist, /etc wins. periodt.

The tuned.conf configures the profile, and it's in plain old ini-file format. You already know ini. You've met ini. Ini is your friend. 🫶

---

🌸 MAIN SECTION 🌸

The main section is called [main] and it can contain the following option:

• include= — includes a profile with the given name. This is how you base a new profile on an already existing one, like building your fit on top of a base layer. If there are conflicting parameters between the new profile and the base profile, the parameters from the new profile are used. New profile wins, no debate. 💅

---

🎀 PLUGINS 🎀

Every other section defines one plugin. The name of the section becomes the name of the plugin, and it's also used in logs to identify the plugin. So name your sections cute, okay?

There can be only one plugin of a particular type tuning a particular device. If that rule gets broken, conflicts are by default fixed by merging the options of both plugins together. And if you don't want merging? The "replace" option can change that.

Every plugin section can contain the following options:

• type= — the plugin type. Currently there are these 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, so don't come for me if your fave isn't on it. If you installed TuneD through RPM, you can list the upstream plugins with this command:

rpm -ql tuned | grep 'plugins/plugin_.*.py$'

Check the plugins directory returned by that command to see all the plugins — including ones provided by 3rd party packages. 👑

• devices= — a comma separated list of devices which should be tuned by this plugin instance. If you omit this option, all found devices will be tuned. All of them. Every single one. 😭
• replace=1 — if there's a conflict between two plugins (meaning two plugins of the same type are trying to configure the same devices), then the plugin defined last replaces all options defined by the previously defined plugin. Last one in the group chat gets the final word.

Plugins can also have plugin related options. Yes, each one has its own little personality. 🦋

---

🌈 EXAMPLE 🌈

Bestie, this is verbatim. Do not freestyle here.

[main]
# Includes plugins defined in "included" profile.
include=included

# Define my_sysctl plugin
[my_sysctl]
type=sysctl
# This plugin will replace any sysctl plugin defined in "included" profile
replace=1
# 256 KB default performs well experimentally.
net.core.rmem_default = 262144
net.core.wmem_default = 262144

# Define my_script plugin
# Both scripts (profile.sh from this profile and script from "included"
# profile) will be run, because if there is no "replace=1" option the
# default action is merge.
[my_script]
type=script
script=${i:PROFILE_DIR}/profile.sh

---

⭐ SEE ALSO ⭐

• tuned(8)

---

💜 AUTHOR 💜

Written by Jan Kaluža <jkaluza@redhat.com>.

---

🐛 REPORTING BUGS 🐛

Report bugs to https://bugzilla.redhat.com/.

---

and that's the whole page, bestie 💖 go forth, write your profiles, include responsibly, and remember: replace=1 is a flex, not a personality.

Jan Kaluža · 13 Mar 2012 · tuned.conf(5) — yeah that's the source, the version and the date, all wrapped up in a cute little sign-off 🎀✨