Am 04.04.2023 um 13:20 hat Stefan Hajnoczi geschrieben:
> A few Admin Queue commands are submitted during nvme_file_open(). They
> are synchronous since device initialization cannot continue until the
> commands complete.
>
> AIO_WAIT_WHILE() is currently used, but the block/nvme.c code actually
>
On 4/4/23 13:20, Stefan Hajnoczi wrote:
A few Admin Queue commands are submitted during nvme_file_open(). They
are synchronous since device initialization cannot continue until the
commands complete.
AIO_WAIT_WHILE() is currently used, but the block/nvme.c code actually
doesn't rely on the AioCo
On 4/4/23 13:20, Stefan Hajnoczi wrote:
A few Admin Queue commands are submitted during nvme_file_open(). They
are synchronous since device initialization cannot continue until the
commands complete.
AIO_WAIT_WHILE() is currently used, but the block/nvme.c code actually
doesn't rely on the AioCo
A few Admin Queue commands are submitted during nvme_file_open(). They
are synchronous since device initialization cannot continue until the
commands complete.
AIO_WAIT_WHILE() is currently used, but the block/nvme.c code actually
doesn't rely on the AioContext lock. Replace it with
AIO_WAIT_WHILE