Re: [Jack-Devel] jack - audio group - package install

PrevNext  Index
DateTue, 24 Jan 2012 19:22:00 +0200
From Nedko Arnaudov <[hidden] at arnaudov dot name>
ToTobias Hoffmann <[hidden] at thax dot hardliners dot org>
Cc[hidden] at lists dot jackaudio dot org
In-Reply-ToTobias Hoffmann Re: [Jack-Devel] jack - audio group - package install
Follow-UpPaul Davis Re: [Jack-Devel] jack - audio group - package install
Tobias Hoffmann <[hidden]> writes:

>>>>> the kernel doesn't provide many choices. these rights do not exist on
>>>>> a per-process level of granularity. they simply don't.
>>>>>         
>>>> Aren't CGROUPS just what Tobias suggests?
>>>>       
>>> true. i had forgotten our old nemesis, CGROUPs. as long as they are
>>> correctly configured, then cgroups could be used. but they are even
>>> harder to configure than PAM limits, so the likelihood that a distro
>>> will get this right seems small. 
>
> Ok, thanks for the hint. I had been looking at the problem from a
> higher perspective. The two things I had in mind were:
> 1. Either the kernel provides some kind of CAP_* for jackd to call the
> relevant kernel API itself, or
> 2. another (root) process can be used, doing something like
> "set_rt_prio([PID_OF_JACK])" on jacks request.
>
> CGroups are quite another beast, I agree. Still, they might be part of
> a long-term solution.

AFAIK major distros already use cgroups. I think this affects decisions
with short-term implact as well.

-- 
Nedko Arnaudov <GnuPG KeyID: 5D1B58ED>
PrevNext  Index

1327425820.5981_0.ltw:2,a <87aa5d2eyv.fsf at arnaudov dot name>