On 1/9/23 5:44?PM, Bart Van Assche wrote: > On 1/9/23 16:41, Jens Axboe wrote: >> Or, probably better, a stacked scheduler where the bottom one can be zone >> away. Then we can get rid of littering the entire stack and IO schedulers >> with silly blk_queue_pipeline_zoned_writes() or blk_is_zoned_write() etc. > > Hi Jens, > > Isn't one of Damien's viewpoints that an I/O scheduler should not do > the reordering of write requests since reordering of write requests > may involve waiting for write requests, write request that will never > be received if all tags have been allocated? It should be work conservering, it should not wait for anything. If there are holes or gaps, then there's nothing the scheduler can do. My point is that the strict ordering was pretty hacky when it went in, and rather than get better, it's proliferating. That's not a good direction. -- Jens Axboe
