1 |
On 2014-08-13, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
2 |
> On 13/08/2014 19:21, Grant Edwards wrote: |
3 |
|
4 |
>> This is not Gentoo specific, and while I'm doing my prototyping and |
5 |
>> development on a Gentoo system, the eventual target is not going to |
6 |
>> be running Gentoo -- so feel free to ignore this thread or throw |
7 |
>> things at me. |
8 |
>> |
9 |
>> I'm trying to figure out how to synchronize threads which may be in |
10 |
>> different processes. Basically, I want thread A to be able to wake up |
11 |
>> any number of other threads B, C, D, ... who are all blocking until A |
12 |
>> says "go" (and who may or may not be in other processes). |
13 |
> |
14 |
> Sounds like you a "one talker - many listeners" model. |
15 |
|
16 |
For that particular case, yes. |
17 |
|
18 |
> Have you considered a really simple solution like dbus? |
19 |
|
20 |
I don't know if I would call dbus "really simple". :) |
21 |
|
22 |
My current implementation uses Unix domain sockets (which is what dbus |
23 |
usually uses, isn't it?), and I'm trying to figure out how to reduce |
24 |
overhead and latency. dbus would add even more overhead (it has code |
25 |
to deal with byte ordering, serial/cookies, and various other features |
26 |
and abstractions). I'm not sure it's really practical for |
27 |
high-frequency events (e.g 100-200 events per second). |
28 |
|
29 |
-- |
30 |
Grant Edwards grant.b.edwards Yow! I've got a COUSIN |
31 |
at who works in the GARMENT |
32 |
gmail.com DISTRICT ... |