[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [RFC PATCH 00/11] Block layer thread-safety, next part
|
From: |
Stefan Hajnoczi |
|
Subject: |
Re: [Qemu-devel] [RFC PATCH 00/11] Block layer thread-safety, next part |
|
Date: |
Mon, 10 Jul 2017 17:25:05 +0100 |
|
User-agent: |
Mutt/1.8.0 (2017-02-23) |
On Thu, Jul 06, 2017 at 06:38:17PM +0200, Paolo Bonzini wrote:
> Here, patches 1-6 make the remaining part of the block layer thread safe.
> Patches 7-11 start removing aio_context_acquire/release, so the line
> count goes down instead of up.
>
> This is the penultimate series. The remaining part makes virtio-blk,
> virtio-scsi and block jobs thread safe, so that the AioContext lock
> can go away altogether.
Looks promising. I replied to the last patch with my overall concern
about this series.
Stefan
signature.asc
Description: PGP signature
- Re: [Qemu-devel] [PATCH 06/11] block: add a few more notes on locking, (continued)
- [Qemu-devel] [PATCH 09/11] block/replication: do not acquire AioContext, Paolo Bonzini, 2017/07/06
- [Qemu-devel] [PATCH 07/11] block: do not acquire AioContext in check_to_replace_node, Paolo Bonzini, 2017/07/06
- [Qemu-devel] [PATCH 10/11] block: do not take AioContext around reopen, Paolo Bonzini, 2017/07/06
- [Qemu-devel] [PATCH 11/11] block/snapshot: do not take AioContext lock, Paolo Bonzini, 2017/07/06
- Re: [Qemu-devel] [RFC PATCH 00/11] Block layer thread-safety, next part, no-reply, 2017/07/06
- Re: [Qemu-devel] [RFC PATCH 00/11] Block layer thread-safety, next part,
Stefan Hajnoczi <=