On Wed, 27 Nov 2002, Paul Davis wrote:
> >Sorry, it's not as easy as you've described. It's not possible to invoke
> >any user code from the kernel code directly. There is a scheduler which is
> >informed that a task has been woken up. It depends on scheduler when the
> >task is really invoked. It's quite same as for the r/w model where the
> >application is notified over poll that something occured.
>
> i think we can consider the behaviour of the kernel scheduler when it
> schedules a SCHED_FIFO task after an audio interface interrupt has
> woken it to be very, very close to the kind of callback system james
> is describing. ditto for any kind of wakeup of a SCHED_FIFO task
> (e.g. when its woken by a write to pipe, or a signal).
>
> its not perfect, as i am very disappointed to discover, but its also
> very close.
If you have more processes with same priority, the time gaps might be
noticable as well.
Jaroslav
-----
Jaroslav Kysela <[EMAIL PROTECTED]>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs
-------------------------------------------------------
This SF.net email is sponsored by: Get the new Palm Tungsten T
handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
_______________________________________________
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
