[tuned] #47: Create new plugin for process scheduling/priority tuning
by fedora-badges
#47: Create new plugin for process scheduling/priority tuning
--------------------------+--------------------
Reporter: jeder | Owner:
Type: enhancement | Status: new
Priority: major | Component: daemon
Version: 2.0 | Keywords:
Blocked By: | Blocking:
--------------------------+--------------------
We have an init-based service now that, upon boot, applies some scheduler
tuning to regexes matching threads.
Below is an example:
# Format is: <groupname>:<sched>:<prio>:affinity:<regex>
kthreads:*:1:*:\[.*\]$
watchdog:f:99:*:\[watchdog.*\]
migration:f:99:*:\[migration\/.*\]
softirq:f:70:*:\[.*(softirq|sirq).*\]
softirq-net-tx:f:75:*:\[(softirq|sirq)-net-tx.*\]
softirq-net-rx:f:75:*:\[(softirq|sirq)-net-rx.*\]
softirq-sched:f:1:*:\[(softirq|sirq)-sched\/.*\]
rpciod:f:65:*:\[rpciod.*\]
lockd:f:65:*:\[lockd.*\]
nfsd:f:65:*:\[nfsd.*\]
hardirq:f:85:*:\[(irq|IRQ)[\-_/].*\]
We would like to move this functionality from the init system to a tuned
profile, but it doesn't seem possible with the current tuned
capabilities/plugins.
In addition to one-shot tuning during profile load, there is also a use-
case for monitoring new processes that are created, and applying this
tuning.
This could be a watchdog/scanning behavior in tuned daemon (not preferred
because it creates background noise), or something more clever using perf
events or even LD_PRELOAD of exec function call.
--
Ticket URL: <https://fedorahosted.org/tuned/ticket/47>
tuned <https://fedorahosted.org/tuned/>
A daemon that performs monitoring and adaptive configuration of devices in the system.
9 years, 6 months
[tuned] #45: Provide white/blacklist for tunings
by fedora-badges
#45: Provide white/blacklist for tunings
---------------------+--------------------
Reporter: jeder | Owner:
Type: defect | Status: new
Priority: major | Component: daemon
Version: 2.0 | Keywords:
Blocked By: | Blocking:
---------------------+--------------------
Tuned sets readahead for all devices to the same value. But a system
might have different storage devices attached that require different
readahead values (i.e. local storage vs flash).
Tuned should provide a way for users to specify readaheads on a per-device
basis. This could be implemented as a regex in the profile tuned.conf.
i.e.
readahead={4096,devices=*}
readahead={8192,devices=fio*}
Other example tunings that need this feature:
- I/O scheduler
- Filesystem barriers
--
Ticket URL: <https://fedorahosted.org/tuned/ticket/45>
tuned <https://fedorahosted.org/tuned/>
A daemon that performs monitoring and adaptive configuration of devices in the system.
9 years, 11 months
[tuned] #44: Resolve interaction between tuned and udev
by fedora-badges
#44: Resolve interaction between tuned and udev
---------------------+--------------------
Reporter: jeder | Owner:
Type: defect | Status: new
Priority: major | Component: daemon
Version: 2.0 | Keywords:
Blocked By: | Blocking:
---------------------+--------------------
Vendors use udev rules to apply tunings specific to their
application/hardware. Tuned may overwrite these tunings.
For example, the user specifies a readahead value of 8192 below. By
default, tuned would overwrite this with 4096. Tuned should not overwrite
these tunings.
cat /etc/udev/rules.d/80-readahead.rules
# increase readahead for sd* devices
ACTION=="add", KERNEL=="sd*", ATTR{bdi/read_ahead_kb}="8192"
--
Ticket URL: <https://fedorahosted.org/tuned/ticket/44>
tuned <https://fedorahosted.org/tuned/>
A daemon that performs monitoring and adaptive configuration of devices in the system.
9 years, 11 months