... | ... | @@ -51,10 +51,22 @@ Use `libpipewire-module-rtkit` or `libpipewire-module-rt` to select the RTKit or |
|
|
- `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.
|
|
|
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
|
|
|
|
|
|
Real-time priority limits are usually stored in `/etc/security/limits.conf` and `/etc/security/limits.d/`. The best option is to add a new file `95-pipewire.conf` in `/etc/security/limits.d/` with this content:
|
|
|
|
|
|
```
|
|
|
# Default limits for users of pipewire
|
|
|
@pipewire - rtprio 95
|
|
|
@pipewire - priority -19
|
|
|
@pipewire - memlock 4194304
|
|
|
```
|
|
|
Then add your user to the pipewire group so that you can use these priorities.
|
|
|
|
|
|
# RTkit
|
|
|
|
|
|
RTKit can be configured by passing extra arguments to the `/usr/libexec/rtkit-daemon` process. You can try `/usr/libexec/rtkit-daemon --help` to see the options.
|
... | ... | |