> This series lets interested callers ask for an -EAGAIN return from the
> chardev backends (only unix and tcp sockets as of now) to implement
> their own flow control.

As mentioned previously, I think this is a bad idea.  The device has no useful 
way of determining when to transmit the rest of the data.

What you really want is an asynchronous transmit API.

Paul


Reply via email to