[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH RFC 0/4] hw/block/nvme: convert ad-hoc aio tracking to aiocbs
From: |
Klaus Jensen |
Subject: |
[PATCH RFC 0/4] hw/block/nvme: convert ad-hoc aio tracking to aiocbs |
Date: |
Tue, 2 Mar 2021 12:10:36 +0100 |
From: Klaus Jensen <k.jensen@samsung.com>
The nvme device currently uses an ad-hoc approach to tracking AIO
completion when a request results in multiple issued AIOs.
This series convert those operations (DSM, Copy, Flush and Zone Reset)
to use "proper" QEMU AIOCB processing instead. This requires more code,
but the end result of this is that we gain proper cancellation support
(something that the device would not do correctly in the existing ad-hoc
approach, and something that would have required more code anyway).
This series makes SQ deletions "just work" and allows Abort to be
implemented such that it actually does something.
Marking RFC, since I've not really done anything with QEMU AIOs and BHs
on this level before, so I'd really like some block-layer eyes on it.
Klaus Jensen (4):
hw/block/nvme: convert dsm to aiocb
hw/block/nvme: convert copy to aiocb
hw/block/nvme: convert flush to aiocb
hw/block/nvme: convert zone reset to aiocb
hw/block/nvme.c | 945 ++++++++++++++++++++++++------------------
hw/block/trace-events | 2 +-
2 files changed, 537 insertions(+), 410 deletions(-)
--
2.30.1
- [PATCH RFC 0/4] hw/block/nvme: convert ad-hoc aio tracking to aiocbs,
Klaus Jensen <=
[PATCH RFC 4/4] hw/block/nvme: convert zone reset to aiocb, Klaus Jensen, 2021/03/02
Re: [PATCH RFC 0/4] hw/block/nvme: convert ad-hoc aio tracking to aiocbs, Stefan Hajnoczi, 2021/03/08