Re: [Qemu-devel] ????: [PATCH v2 06/43] Return path: socket_writev_buffer:?Block even on non-blocking fd's

[Dr. David Alan Gilbert]

* chenliang (T) (address@hidden) wrote:
> 
> From: "Dr. David Alan Gilbert" <address@hidden>
> 
> The return path uses a non-blocking fd so as not to block waiting for the 
> (possibly broken) destination to finish returning a message, however we still 
> want outbound data to behave in the same way and block.
> 
> Signed-off-by: Dr. David Alan Gilbert <address@hidden>
> 
> Hi David
>   It is confusing why don't use blocking fd?

I want to make sure that if the destination guest hung during
sending a return path command, that the source wouldn't block
the main thread (in which I'm currently processing the RP commands).

Paolo made a suggestion to move the RP processing to a separate
thread, which would also avoid the problem, and I'll be trying that.

Dave

> Best regards
--
Dr. David Alan Gilbert / address@hidden / Manchester, UK