[systemd-devel] [lennart at kemper.freedesktop.org: [systemd-commits] src/pam-module.c]

[fykcee1 at gmail.com]

2011/2/14 Andrey Borzenkov <arvidjaar at mail.ru>

> RT is about determinism. You need to ensure that task will be able to
> respond in fixed time. If you allow arbitrary, unknown in advance,
> number of tasks share the same limited CPU share, you simply kill
> determinism.
>
> Personally I think that RT should be restricted to limited number of
> tasks that are known in advance; then it is responsibility of
> administrator to allocate their CPU share according to requirements.
>
> >
> > 2011/2/14 Lennart Poettering <lennart at poettering.net>
> >>
> >>
> >> I am not aware of any typical daemon we ship that would use RT
> >> scheduling hence we are keeping the default 'cpu' cgroup sorting for
> >> system daemons enabled. However user applications are more likely to use
> >> RT (for example PA does) and hence we have disabled this for sessions
> >> for now.
> >>
>
> and for reasons outlined above I think that either PA should not
> require RT to run, or we need dedicated system wide PA daemon that can
> be made RT :)
>
Agree in this sense. RT can be seen as 'hardcode' some computing resource
to simulate dedicated hardware, in other words, virtual dsp, should reside
at system scope.




-- 
Regards,

- cee1
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20110214/0b1da54c/attachment.htm>