From 55944e5e40b1be2afc4855d8d2baf4b73d1876b5 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Wed, 10 Apr 2024 22:49:52 +0200 Subject: Adding upstream version 255.4. Signed-off-by: Daniel Baumann --- man/iocost.conf.xml | 78 +++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 78 insertions(+) create mode 100644 man/iocost.conf.xml (limited to 'man/iocost.conf.xml') diff --git a/man/iocost.conf.xml b/man/iocost.conf.xml new file mode 100644 index 0000000..a7fdc66 --- /dev/null +++ b/man/iocost.conf.xml @@ -0,0 +1,78 @@ + + + + + + + iocost.conf + systemd + + + + iocost.conf + 5 + + + + iocost.conf + Configuration files for the iocost solution manager + + + + + /etc/systemd/iocost.conf + /etc/systemd/iocost.conf.d/*.conf + + + + + Description + + This file configures the behavior of iocost, a tool mostly used by + systemd-udevd8 rules + to automatically apply I/O cost solutions to /sys/fs/cgroup/io.cost.*. + + The qos and model values are calculated based on benchmarks collected on the + iocost-benchmark + project and turned into a set of solutions that go from most to least isolated. + Isolation allows the system to remain responsive in face of high I/O load. + Which solutions are available for a device can be queried from the udev metadata attached to it. By + default the naive solution is used, which provides the most bandwidth. + + + + + + Options + + All options are configured in the [IOCost] section: + + + + + TargetSolution= + + Chooses which I/O cost solution (identified by named string) should be used + for the devices in this system. The known solutions can be queried from the udev metadata + attached to the devices. If a device does not have the specified solution, the first one + listed in IOCOST_SOLUTIONS is used instead. + + E.g. TargetSolution=isolated-bandwidth. + + + + + + + + See Also + + udevadm8, + The iocost-benchmarks github project, + The resctl-bench + documentation details how the values are obtained + + + + -- cgit v1.2.3