RLIMIT_MEMLOCK warning since ~0.3.20
As of at least f03deb53 i do get
Feb 07 21:10:24 db systemd: Started PipeWire PulseAudio. Feb 07 21:11:15 db pipewire-pulse: Failed to mlock memory 0x7fa8c3730000 32832: This is not a problem but for best performance, consider increasing RLIMIT_MEMLOCK
Also i notice rare but occasional crackling. That i also had when started using pipewire but vanished when i set up memlock limits. So i figure that might correlate.
$ cat /etc/security/limits.d/99-realtime-privileges.conf @realtime - rtprio 98 @realtime - memlock unlimited
$ id | grep -c \(realtime\) 1
$ ulimit -a core file size (blocks, -c) unlimited data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 128010 max locked memory (kbytes, -l) unlimited max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 98 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 128010 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited
The pipewire* processes run under the correct user.
A trivial example program with mlock(..., 32832) works fine. Tested also with 0.3.21-1 from Arch as well as 37d8cbd5.