diff options
| author | Stefan Hajnoczi <stefanha@redhat.com> | 2023-05-30 14:09:58 -0400 |
|---|---|---|
| committer | Stefan Hajnoczi <stefanha@redhat.com> | 2023-06-01 07:34:03 -0400 |
| commit | 076682885d6fe521ed005b988fde6a67ec6818df (patch) | |
| tree | 9b1e887119f0f3aff92f0fb2dccff8235bdf1730 /bsd-user | |
| parent | 6a6da231b7076b8ed5409c4745e11cb14d962194 (diff) | |
| download | qemu-076682885d6fe521ed005b988fde6a67ec6818df.zip qemu-076682885d6fe521ed005b988fde6a67ec6818df.tar.gz qemu-076682885d6fe521ed005b988fde6a67ec6818df.tar.bz2 | |
block/linux-aio: convert to blk_io_plug_call() API
Stop using the .bdrv_co_io_plug() API because it is not multi-queue
block layer friendly. Use the new blk_io_plug_call() API to batch I/O
submission instead.
Note that a dev_max_batch check is dropped in laio_io_unplug() because
the semantics of unplug_fn() are different from .bdrv_co_unplug():
1. unplug_fn() is only called when the last blk_io_unplug() call occurs,
not every time blk_io_unplug() is called.
2. unplug_fn() is per-thread, not per-BlockDriverState, so there is no
way to get per-BlockDriverState fields like dev_max_batch.
Therefore this condition cannot be moved to laio_unplug_fn(). It is not
obvious that this condition affects performance in practice, so I am
removing it instead of trying to come up with a more complex mechanism
to preserve the condition.
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Acked-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
Message-id: 20230530180959.1108766-6-stefanha@redhat.com
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Diffstat (limited to 'bsd-user')
0 files changed, 0 insertions, 0 deletions