[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 4/4] virtio-blk: don't lock AioContext in the submission code
|
From: |
Eric Blake |
|
Subject: |
Re: [PATCH 4/4] virtio-blk: don't lock AioContext in the submission code path |
|
Date: |
Thu, 14 Sep 2023 12:27:13 -0500 |
|
User-agent: |
NeoMutt/20230517 |
On Thu, Sep 14, 2023 at 10:01:01AM -0400, Stefan Hajnoczi wrote:
> There is no need to acquire the AioContext lock around blk_aio_*() or
> blk_get_geometry() anymore. I/O plugging (defer_call()) also does not
> require the AioContext lock anymore.
>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
> hw/block/virtio-blk.c | 5 -----
> 1 file changed, 5 deletions(-)
>
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
- [PATCH 0/4] virtio-blk: prepare for the multi-queue block layer, Stefan Hajnoczi, 2023/09/14
- [PATCH 4/4] virtio-blk: don't lock AioContext in the submission code path, Stefan Hajnoczi, 2023/09/14
- Re: [PATCH 4/4] virtio-blk: don't lock AioContext in the submission code path,
Eric Blake <=
- [PATCH 2/4] virtio-blk: add lock to protect s->rq, Stefan Hajnoczi, 2023/09/14
- [PATCH 3/4] virtio-blk: don't lock AioContext in the completion code path, Stefan Hajnoczi, 2023/09/14
- [PATCH 1/4] block/file-posix: set up Linux AIO and io_uring in the current thread, Stefan Hajnoczi, 2023/09/14
- Re: [PATCH 0/4] virtio-blk: prepare for the multi-queue block layer, Michael S. Tsirkin, 2023/09/15