search for: f7728002c1c7

...where the hw_queue is guaranteed to get > started by virtblk_done() before when it makes sense to carry on > submitting requests. Let us also remove a stale comment. > > Signed-off-by: Halil Pasic <pasic at linux.ibm.com> > Cc: Jens Axboe <axboe at kernel.dk> > Fixes: f7728002c1c7 ("virtio_ring: fix return code on DMA mapping fails") > --- > > I'm in doubt with regards to the Fixes tag. The thing is, virtio-blk > probably made an assumption on virtqueue_add: the failure is either > because the virtqueue is full, or the failure is fatal. In both...

...h indicates a full virtqueue, where the hw_queue is guaranteed to get started by virtblk_done() before when it makes sense to carry on submitting requests. Let us also remove a stale comment. Signed-off-by: Halil Pasic <pasic at linux.ibm.com> Cc: Jens Axboe <axboe at kernel.dk> Fixes: f7728002c1c7 ("virtio_ring: fix return code on DMA mapping fails") --- I'm in doubt with regards to the Fixes tag. The thing is, virtio-blk probably made an assumption on virtqueue_add: the failure is either because the virtqueue is full, or the failure is fatal. In both cases it seems acceptable...

Two patches are handling new edge cases introduced by doing DMA mappings (which can fail) in virtio core. I stumbled upon this while stress testing I/O for Protected Virtual Machines. I deliberately chose a tiny swiotlb size and have generated load with fio. With more than one virtio-blk disk in use I experienced hangs. The goal of this series is to fix those hangs. Halil Pasic (2):

Two patches are handling new edge cases introduced by doing DMA mappings (which can fail) in virtio core. I stumbled upon this while stress testing I/O for Protected Virtual Machines. I deliberately chose a tiny swiotlb size and have generated load with fio. With more than one virtio-blk disk in use I experienced hangs. The goal of this series is to fix those hangs. Halil Pasic (2):