On Sun, 21.06.09 20:58, Fernando Lopez-Lezcano (nando@ccrma.Stanford.EDU) wrote:
> > > The question is relevant, I think, as the kernels that I use (Planet
Again, the worst thing that happens is that you need to bump
RLIMIT_RTPRIO for your user, as you always did. rtkit doesn't take
Kernel that lacks SCHED_RESET_ON_FORK: RLIMIT_RTPRIO is what matters.
Kernel that has SCHED_RESET_ON_FORK: RLIMIT_RTPRIO still matters when
it is set, rtkit is used as fallback.
Also note that supporting rtkit often enough doesn't add a build-time
dep to you application and the runtime dependency is very soft too: if
it isn't found it's not used, that's all.
> > > > can set that flag when entering SCHED_RR scheduling and this will
In JACK's sources the only place where I see fiddling with the
scheduler is in jack_acquire_real_time_scheduling(), which takes a
pthread_t. pthread_t is process local, so I am pretty sure JACK
doesn't try to change scheduling of out-of-process threads. This
should hence be perfectly compatible with the rtkit model.
Lennart Poettering Red Hat, Inc.
lennart [at] poettering [dot] net
http://0pointer.net/lennart/ GnuPG 0x1A015CC4
Linux-audio-dev mailing list