[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH 07/16] coroutine-lock: reschedule coroutine on t
From: |
Stefan Hajnoczi |
Subject: |
Re: [Qemu-devel] [PATCH 07/16] coroutine-lock: reschedule coroutine on the AioContext it was running on |
Date: |
Wed, 18 Jan 2017 15:26:35 +0000 |
User-agent: |
Mutt/1.7.1 (2016-10-04) |
On Fri, Jan 13, 2017 at 02:17:22PM +0100, Paolo Bonzini wrote:
> As a small step towards the introduction of multiqueue, we want
> coroutines to remain on the same AioContext that started them,
> unless they are moved explicitly with e.g. aio_co_schedule. This patch
> avoids that coroutines switch AioContext when they use a CoMutex.
> For now it does not make much of a difference, because the CoMutex
> is not thread-safe and the AioContext itself is used to protect the
> CoMutex from concurrent access. However, this is going to change.
>
> Signed-off-by: Paolo Bonzini <address@hidden>
> ---
> util/qemu-coroutine-lock.c | 5 ++---
> util/trace-events | 1 -
> 2 files changed, 2 insertions(+), 4 deletions(-)
Reviewed-by: Stefan Hajnoczi <address@hidden>
signature.asc
Description: PGP signature
- Re: [Qemu-devel] [PATCH 05/16] io: make qio_channel_yield aware of AioContexts, (continued)
[Qemu-devel] [PATCH 04/16] io: add methods to set I/O handlers on AioContext, Paolo Bonzini, 2017/01/13
[Qemu-devel] [PATCH 07/16] coroutine-lock: reschedule coroutine on the AioContext it was running on, Paolo Bonzini, 2017/01/13
- Re: [Qemu-devel] [PATCH 07/16] coroutine-lock: reschedule coroutine on the AioContext it was running on,
Stefan Hajnoczi <=
[Qemu-devel] [PATCH 01/16] aio: introduce aio_co_schedule and aio_co_wake, Paolo Bonzini, 2017/01/13
Re: [Qemu-devel] [PATCH 01/16] aio: introduce aio_co_schedule and aio_co_wake, Stefan Hajnoczi, 2017/01/18
[Qemu-devel] [PATCH 06/16] nbd: do not block on partial reply header reads, Paolo Bonzini, 2017/01/13