... | @@ -30,31 +30,8 @@ The configuration of the realtime priorities and the implementation can be done |
... | @@ -30,31 +30,8 @@ The configuration of the realtime priorities and the implementation can be done |
|
- `/usr/share/pipewire/client-rt.conf` for the PipeWire native client settings
|
|
- `/usr/share/pipewire/client-rt.conf` for the PipeWire native client settings
|
|
- `/usr/share/pipewire/jack.conf` for the PipeWire JACK clients
|
|
- `/usr/share/pipewire/jack.conf` for the PipeWire JACK clients
|
|
|
|
|
|
The relevant module is enabled in the `context.modules` section:
|
|
The relevant module is enabled in the `context.modules` section, see
|
|
|
|
[module-rt](https://docs.pipewire.org/page_module_rt.html) documentation.
|
|
```
|
|
|
|
context.modules = [
|
|
|
|
# boost the data thread priority.
|
|
|
|
{ name = libpipewire-module-rt
|
|
|
|
args = {
|
|
|
|
#nice.level = -11
|
|
|
|
#rt.prio = 88
|
|
|
|
#rt.time.soft = 2000000
|
|
|
|
#rt.time.hard = 2000000
|
|
|
|
}
|
|
|
|
flags = [ ifexists nofail ]
|
|
|
|
}
|
|
|
|
....
|
|
|
|
```
|
|
|
|
Use `libpipewire-module-rt` to select the RTKit and native thread implementation.
|
|
|
|
|
|
|
|
- `nice.level` this will be the nice value set for the application thread. It improves performance of the communication with the pipewire daemon.
|
|
|
|
- `rt.prio` this is the realtime priority of the data thread. Higher values are higher priority.
|
|
|
|
- `rt.time.soft`, `rt.time.hard` The amount of CPU time an RT thread can consume without doing any blocking calls before the kernel kills the thread. This is a safety measure to avoid lockups of the complete system when some thread consumes 100%.
|
|
|
|
|
|
|
|
The native implementation will use FIFO scheduling with the indicated priorities. Your user will need appropriate RLIMIT to be able to set priorities.
|
|
|
|
|
|
|
|
The RTKit module might not be able to configure the given values, depending on the limits as configured in RTKit.
|
|
|
|
|
|
|
|
# RLIMITs
|
|
# RLIMITs
|
|
|
|
|
... | | ... | |