Re: [Qemu-block] [PATCH 1/3] io: Yield rather than wait when already in coroutine

2017-09-06 Thread Eric Blake
On 09/06/2017 03:50 AM, Daniel P. Berrange wrote: > On Tue, Sep 05, 2017 at 02:11:12PM -0500, Eric Blake wrote: >> The new qio_channel_{read,write}{,v}_all functions are documented >> as yielding until data is available. When used on a blocking >> channel, this yield is done via qio_channel_wait()

Re: [Qemu-block] [PATCH 1/3] io: Yield rather than wait when already in coroutine

2017-09-06 Thread Daniel P. Berrange
On Tue, Sep 05, 2017 at 02:11:12PM -0500, Eric Blake wrote: > The new qio_channel_{read,write}{,v}_all functions are documented > as yielding until data is available. When used on a blocking > channel, this yield is done via qio_channel_wait() which spawns > a new coroutine under the hood (so it i

[Qemu-block] [PATCH 1/3] io: Yield rather than wait when already in coroutine

2017-09-05 Thread Eric Blake
The new qio_channel_{read,write}{,v}_all functions are documented as yielding until data is available. When used on a blocking channel, this yield is done via qio_channel_wait() which spawns a new coroutine under the hood (so it is the new entry point that yields as needed); but if we are already