Urk, sorry I didn't quite get the implications of this statement: The kfifo is used only on the receive path because of the asynchronous > callbacks. The > Tx-path is synchronous, the copy is attempted directly on the vring buffers >
That means that kfifo doesn't exist on send so the only available solution appears to be calling rpmsg_trysend when in O_NONBLOCK mode. That will hit the full vring buffers and should bounce back immediately with ENOMEM. Thanks. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/dcbb9c5a-229a-481f-8ea0-11a8735ac095o%40googlegroups.com.
