Bug#507248: realtime settings

2009-03-08 Thread Steve Langasek
On Sun, Mar 08, 2009 at 05:15:50PM +0100, Reinhard Tartler wrote: > a...@drcomp.erfurt.thur.de (Adrian Knoth) writes: > > On Sat, Mar 07, 2009 at 02:47:28PM -0800, Steve Langasek wrote: > >> ardour uses mlock() on its ring buffers to ensure they're available in > >> physical memory. What if in o

Bug#507248: realtime settings

2009-03-08 Thread Reinhard Tartler
a...@drcomp.erfurt.thur.de (Adrian Knoth) writes: > On Sat, Mar 07, 2009 at 02:47:28PM -0800, Steve Langasek wrote: > >> ardour uses mlock() on its ring buffers to ensure they're available in >> physical memory. What if in order to meet this requirement, the kernel >> instead swaps out the proces

Bug#507248: realtime settings

2009-03-08 Thread Adrian Knoth
On Sat, Mar 07, 2009 at 02:47:28PM -0800, Steve Langasek wrote: > ardour uses mlock() on its ring buffers to ensure they're available in > physical memory. What if in order to meet this requirement, the kernel > instead swaps out the process stack and has to page that back in? What if > it drops

Bug#507248: realtime settings

2009-03-07 Thread Steve Langasek
On Sat, Mar 07, 2009 at 10:53:26PM +0100, Adrian Knoth wrote: > On Sat, Mar 07, 2009 at 01:14:26PM -0800, Steve Langasek wrote: > > > First: I'm going to reassign this bug to libpam-modules, since > > > /etc/security/limits.conf isn't owned by jackd. > > > Second: There's usually no need to limit

Bug#507248: realtime settings

2009-03-07 Thread Adrian Knoth
On Sat, Mar 07, 2009 at 01:14:26PM -0800, Steve Langasek wrote: > > First: I'm going to reassign this bug to libpam-modules, since > > /etc/security/limits.conf isn't owned by jackd. > > > Second: There's usually no need to limit the size of the maximum locked > > memory. Actually, some programs

Bug#507248: realtime settings

2009-03-07 Thread Steve Langasek
reassign 507248 jackd thanks On Sat, Mar 07, 2009 at 02:47:37PM +0100, Adrian Knoth wrote: > First: I'm going to reassign this bug to libpam-modules, since > /etc/security/limits.conf isn't owned by jackd. > Second: There's usually no need to limit the size of the maximum locked > memory. Actual

Bug#507248: realtime settings

2009-03-07 Thread Adrian Knoth
Hi! First: I'm going to reassign this bug to libpam-modules, since /etc/security/limits.conf isn't owned by jackd. Second: There's usually no need to limit the size of the maximum locked memory. Actually, some programs (ardour?) even print a warning if you do so. Third: with realtime prio, I've