[linux-audio-dev] Re: [linux-audio-user] Please test the RT rlimits patch for audio

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> Jack O'Quin wrote:
>>Perhaps someone can explain how to do this using PAM.  I believe you
>>set the `memlock' option in `/etc/security/limits.conf', somehow.


"Shayne O'Connor" <forums@xxxxxxxxxxxxxxxxxxxxxx> writes:
> yep, this works for me ... here are my PAM settings in limits.conf:
>
> <domain> <type> <item>         <value>
>
> @audio          -      rt_priority      100
> @audio          -      nice              10
> @audio          -      memlock        250000
>
> i've got a total of 512mb RAM, so i thought half of that would be
> appropriate ... is this setting ok/too high/too low?

Maybe.  Depends on what JACK clients you run (they all get mlocked).
Ardour takes up quite a lot of space.  If you're willing to grant the
max priority (100), your system is probably a dedicated audio
workstation, so you might just as well make memlock "unlimited".

There is also the -m (--no-mlock) JACK option that disables memory
locking even with the -R (--realtime) option.
-- 
  joq

[Index of Archives]     [Linux Sound]     [ALSA Users]     [Pulse Audio]     [ALSA Devel]     [Sox Users]     [Linux Media]     [Kernel]     [Photo Sharing]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux