Re: [PATCH v2 27/28] block: Do not force select mq-deadline with CONFIG_BLK_DEV_ZONED

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Damien Le Moal <dlemoal@xxxxxxxxxx>, linux-block@xxxxxxxxxxxxxxx, Jens Axboe <axboe@xxxxxxxxx>, linux-scsi@xxxxxxxxxxxxxxx, "Martin K . Petersen" <martin.petersen@xxxxxxxxxx>, dm-devel@xxxxxxxxxxxxxxx, Mike Snitzer <snitzer@xxxxxxxxxx>
Subject: Re: [PATCH v2 27/28] block: Do not force select mq-deadline with CONFIG_BLK_DEV_ZONED
From: Bart Van Assche <bvanassche@xxxxxxx>
Date: Mon, 25 Mar 2024 15:29:30 -0700
Cc: Christoph Hellwig <hch@xxxxxx>
In-reply-to: <20240325044452.3125418-28-dlemoal@kernel.org>
User-agent: Mozilla Thunderbird

On 3/24/24 21:44, Damien Le Moal wrote:

Now that zone block device write ordering control does not depend
anymore on mq-deadline and zone write locking, there is no need to force
select the mq-deadline scheduler when CONFIG_BLK_DEV_ZONED is enabled.


Reviewed-by: Bart Van Assche <bvanassche@xxxxxxx>

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

References:
- [PATCH v2 00/28] Zone write plugging
  - From: Damien Le Moal
- [PATCH v2 27/28] block: Do not force select mq-deadline with CONFIG_BLK_DEV_ZONED
  - From: Damien Le Moal

Prev by Date: Re: [PATCH v2 26/28] block: Remove zone write locking
Next by Date: Re: [External] : [PATCH 00/28] Remove PCI_IRQ_LEGACY
Previous by thread: [PATCH v2 27/28] block: Do not force select mq-deadline with CONFIG_BLK_DEV_ZONED
Next by thread: Re: [PATCH v2 27/28] block: Do not force select mq-deadline with CONFIG_BLK_DEV_ZONED
Index(es):
- Date
- Thread

[Index of Archives] [SCSI Target Devel] [Linux SCSI Target Infrastructure] [Kernel Newbies] [IDE] [Security] [Git] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux ATA RAID] [Linux IIO] [Samba] [Device Mapper]

Powered by Linux