9 Jul
2003
9 Jul
'03
5:58 p.m.
Hi Jacob,
Hi LAD members,
On Mon, Jul 07, 2003 at 04:50:45PM -0600, jacob robbins
wrote:
> deadlock. You forgot to mention one other method for achieving this
> communication; System V ipc messages, which i prefer because they don't
> lock (if used right) and they are simple. See the man pages for msgget,
> msgsnd, msgrcv.
What do you mean by "if used right"?
It's pretty simple: The realtime thread must always try to get
messages in non-blocking mode.
Meanwhile, the UI thread blocks waiting for the receipt of a different
message from the realtime thread indicating that the requested issue has
been handled. Of course the issues must be carefully constructed so that
the realtime thread can handle them without allocating any memory or
doing too many long loops.
-jacob robbins.....
12 Jul
12 Jul
7:11 a.m.
New subject: [linux-audio-dev] It's been more than a year... Have things improved?
Hi Jacob,
hi LAD,
On Wed, Jul 09, 2003 at 01:45:12PM -0600, jacob robbins wrote:
[Sys V messages are usable for realtime, if used right]
So the typical realtime claims apply and this is another example
that good solutions are simple ;-)
Thanks and regards
Ingo Oeser
What do you
mean by "if used right"?
It's pretty simple: The realtime thread must always try to get
messages in non-blocking mode.
7834
days inactive
7837
days old
linux-audio-dev@lists.linuxaudio.org
1 comments
2 participants
participants (2)
-
Ingo Oeser -
jacob robbins