Message ID | 20240328004409.594888-18-dlemoal@kernel.org (mailing list archive) |
---|---|
State | Superseded |
Headers | show |
Series | Zone write plugging | expand |
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
On 3/27/24 5:43 PM, Damien Le Moal wrote: > With zone write plugging enabled at the block layer level, any zone zone -> zoned Anyway: Reviewed-by: Bart Van Assche <bvanassche@acm.org>
On 3/27/24 17:43, Damien Le Moal wrote: > With zone write plugging enabled at the block layer level, any zone > device can only ever see at most a single write operation per zone. > There is thus no need to request a block scheduler with strick per-zone > sequential write ordering control through the ELEVATOR_F_ZBD_SEQ_WRITE > feature. Removing this allows using a zoned null_blk device with any > scheduler, including "none". > > Signed-off-by: Damien Le Moal<dlemoal@kernel.org> > Reviewed-by: Hannes Reinecke<hare@suse.de> Looks good. Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com> -ck
diff --git a/drivers/block/null_blk/zoned.c b/drivers/block/null_blk/zoned.c index 1689e2584104..8e217f8fadcd 100644 --- a/drivers/block/null_blk/zoned.c +++ b/drivers/block/null_blk/zoned.c @@ -165,7 +165,6 @@ int null_register_zoned_dev(struct nullb *nullb) struct request_queue *q = nullb->q; blk_queue_flag_set(QUEUE_FLAG_ZONE_RESETALL, q); - blk_queue_required_elevator_features(q, ELEVATOR_F_ZBD_SEQ_WRITE); nullb->disk->nr_zones = bdev_nr_zones(nullb->disk->part0); return blk_revalidate_disk_zones(nullb->disk, NULL); }