[zeromq-dev] zmq_poll versus zloop reactor: different semantics - how to resolve?
mail17 at mah.priv.at
Thu Sep 27 22:55:00 CEST 2012
Am 27.09.2012 um 22:23 schrieb Michael Haberler:
> I think I'll drop named pipes and sysfs, and settle for generic netlink sockets; they work fine with zloop and kernel modules so far and they can be used with uniform adressing kernel/userland as well as user/user which helps with the above setup. I guess I'll add an example for that when I'm done - the documentation on netlink use is a bit impenetrable and there are hardly any good examples.
actually since generic netlink sockets are just that - sockets, another address family and adressing scheme but otherwise very similar to AF_UNIX, pollable and all:
I just looked over the libzmq src/ipc* code and I guess adding them as a socket type wouldnt be all too difficult; the setup is a bit more involved and there's no well-known URI scheme I know of, but that can be made up
what that would give is a bridge to messaging to/from the Linux kernel without major media breaks and contortions like pseudo device drivers for message passing - and without waiting for a kernel-based ZMQ implementation to arrive
I wonder if there's any interest in that - it could be a substantial simplification for the use case I described, but then I'm unsure many folks have that sort of requirement
More information about the zeromq-dev