Hi Gentle Readers, Is it possible to target the use of cpg_dispatch to only flush outbound data or only inbound data, but not both simultaneously? For example, in a single threaded library that would only like to synchronously receive from corosync, it would be nice to only pull data out of the callbacks one at a time based on specifically posting buffers. Would adding a CPG_DISPATCH_SEND and CPG_DISPATCH_RECV be an OK way to provide that functionality?
Would it be generally useful to have an interface (for the zero copy case) that would allow the posting of a iovec to the receive logic to directly receive into the application buffers? How will the interfaces change for the proposed 'zero copy' changes? Is the probe of the file descriptor associated with the umbilical cord between the cpg library and the corosync daemon sufficient to determine the presence of inbound data available from the library? Based on the use of shared memory for much of the communications between the cpg library and the daemon is it possible that data is available for processing yet the file descriptor does not return a positive response to a probe (via select or epoll) on the file descriptor posted to the 'read set' (versus the write or exception set)? Is there a library call that can be made to definitively determine if there are cpg messages available to receive into the application from the library (or conversely, if there are messages pending in the library that have yet to be flushed to the daemon)? Is there a description available for the library calls cpg_iteration_initialize (and friends)? Thank you for your time! dan
_______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
