On 28/11/2014 14:46, Iwan Budi Kusnanto wrote:
> On Fri, Nov 28, 2014 at 7:47 PM, Stefan Hajnoczi wrote:
>> On Fri, Nov 28, 2014 at 01:55:00PM +0700, Iwan Budi Kusnanto wrote:
>>> I meant, does the coroutine will do yield internally when it get
>>> blocked on send(3)?
>>
>> No. In general, QEMU
On Fri, Nov 28, 2014 at 7:47 PM, Stefan Hajnoczi wrote:
> On Fri, Nov 28, 2014 at 01:55:00PM +0700, Iwan Budi Kusnanto wrote:
>> I meant, does the coroutine will do yield internally when it get
>> blocked on send(3)?
>
> No. In general, QEMU will use non-blocking file descriptors so the
> blockin
On Fri, Nov 28, 2014 at 01:55:00PM +0700, Iwan Budi Kusnanto wrote:
> I meant, does the coroutine will do yield internally when it get
> blocked on send(3)?
No. In general, QEMU will use non-blocking file descriptors so the
blocking case does not apply. (You can't use blocking file descriptors
i
I meant, does the coroutine will do yield internally when it get
blocked on send(3)?
On Fri, Nov 28, 2014 at 1:50 PM, Iwan Budi Kusnanto wrote:
> Hi all,
>
> I just found about coroutine in Qemu and it looks good for my use case.
> I have a question about this.
> I found this
> "Coroutines are co
Hi all,
I just found about coroutine in Qemu and it looks good for my use case.
I have a question about this.
I found this
"Coroutines are cooperatively scheduled threads of control. There is
no preemption timer that switches between coroutines periodically,
instead switching between coroutines is
