Message ID | 20230516190238.8401-1-stefanha@redhat.com (mailing list archive) |
---|---|
Headers | show |
Series | block: remove aio_disable_external() API | expand |
Am 16.05.2023 um 21:02 hat Stefan Hajnoczi geschrieben: > The aio_disable_external() API temporarily suspends file descriptor monitoring > in the event loop. The block layer uses this to prevent new I/O requests being > submitted from the guest and elsewhere between bdrv_drained_begin() and > bdrv_drained_end(). > > While the block layer still needs to prevent new I/O requests in drained > sections, the aio_disable_external() API can be replaced with > .drained_begin/end/poll() callbacks that have been added to BdrvChildClass and > BlockDevOps. > > This newer .bdrained_begin/end/poll() approach is attractive because it works > without specifying a specific AioContext. The block layer is moving towards > multi-queue and that means multiple AioContexts may be processing I/O > simultaneously. > > The aio_disable_external() was always somewhat hacky. It suspends all file > descriptors that were registered with is_external=true, even if they have > nothing to do with the BlockDriverState graph nodes that are being drained. > It's better to solve a block layer problem in the block layer than to have an > odd event loop API solution. > > The approach in this patch series is to implement BlockDevOps > .drained_begin/end() callbacks that temporarily stop file descriptor handlers. > This ensures that new I/O requests are not submitted in drained sections. Thanks, applied to the block branch. Kevin