On 01/25/2018 04:14 PM, Julien Blanc wrote: > Le jeudi 25 janvier 2018 à 15:21 +0100, Philippe Gerum a écrit : >> On 01/25/2018 02:43 PM, Julien Blanc wrote: >>> >> There is no provision for I/O multiplexing with alchemy. Only the >> pipe object embeds a RTDM file descriptor which could be passed to >> libcobalt's select() implementation, other resources (e.g. queues, >> buffers etc) don't. > > Thanks for your answer. If i understand correctly, this also means that > it is not recommended to mix both APIs in the same program. For example > a queue created with rt_create_queue cannot be read with > __cobalt_mq_open, am I right ?
Correct. One may use both POSIX and alchemy APIs in the same program though, but calls referring to equivalent objects (e.g. sem, queue, task/threads, etc) are not interchangeable. alchemy provides high-level services built on basic POSIX calls. > >> I would suggest to enable the registry for your application (not for >> the entire POSIX API), as you might not need each and every resource >> to be exposed via a fuse-based fs. > > This is something i'd rather avoid if possible. Though, thanks for the > pointers, at first glance it seems much simpler than what i feared. > It is pretty simple, just not documented. -- Philippe. _______________________________________________ Xenomai mailing list Xenomai@xenomai.org https://xenomai.org/mailman/listinfo/xenomai
