public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Linus Walleij <linus.walleij@linaro.org>, bgurney@redhat.com
Cc: Bart Van Assche <bvanassche@acm.org>, Jan Kara <jack@suse.cz>,
	Paolo Valente <paolo.valente@linaro.org>,
	linux-block <linux-block@vger.kernel.org>,
	linux-mmc <linux-mmc@vger.kernel.org>,
	linux-mtd@lists.infradead.org, Pavel Machek <pavel@ucw.cz>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Richard Weinberger <richard@nod.at>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Artem Bityutskiy <dedekind1@gmail.com>,
	Christoph Hellwig <hch@infradead.org>,
	One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
	Mark Brown <broonie@kernel.org>,
	Damien Le Moal <Damien.LeMoal@wdc.com>,
	Johannes Thumshirn <jthumshirn@suse.de>,
	Oleksandr Natalenko <oleksandr@natalenko.name>,
	Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH v2] block: BFQ default for single queue devices
Date: Mon, 22 Oct 2018 02:12:15 -0600	[thread overview]
Message-ID: <eb60af4f-40bb-da3a-1399-60040d2d2fe2@kernel.dk> (raw)
In-Reply-To: <CACRpkdZZ6RU0aJpUqRn1ndyob1_COhaEs6B9QVRWfa+a60n+Lg@mail.gmail.com>

On 10/19/18 2:42 AM, Linus Walleij wrote:
> On Wed, Oct 17, 2018 at 4:59 PM Bryan Gurney <bgurney@redhat.com> wrote:
> 
>> I feel strongly about the prevention of users running into errors
>> because of an incorrect scheduler default, because I encountered that
>> situation three times in my testing with zoned block devices. The
>> switch to SCSI_MQ would resolve that, since mq-deadline is the
>> default, but in my case, I was using Fedora 28, which disables
>> CONFIG_SCSI_MQ_DEFAULT (which is enabled in the 4.18 kernel), so my
>> default scheduler was cfq.
> 
> I think we should make a patch to the kernel that makes it
> impossible (even from sysfs) to choose a non-zone aware
> scheduler for these devices.
> 
> It's another topic than $SUBJECT patch though. I take this
> into account in this version.

Yes I agree, and I'd be happy to take such a patch. The only matching we
do now is mq-sched for mq-device, and vice versa.  And that will be
going away in 4.21, when there are no more !mq devices that use
scheduling.

If your device is zoned, then you should not be able to switch to a
scheduler that doesn't have support for that. The right approach here
would be to add a capability flag to the IO schedulers.

-- 
Jens Axboe

  parent reply	other threads:[~2018-10-22  8:12 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-15 14:10 [PATCH v2] block: BFQ default for single queue devices Linus Walleij
2018-10-15 14:22 ` Paolo Valente
2018-10-15 14:32 ` Oleksandr Natalenko
2018-10-19  8:33   ` Linus Walleij
2018-10-19  9:26     ` Oleksandr Natalenko
2018-10-15 15:02 ` Bart Van Assche
2018-10-15 18:34   ` Paolo Valente
2018-10-17  5:18     ` Paolo Valente
2018-10-16 16:14   ` Federico Motta
2018-10-16 16:26     ` Paolo Valente
2018-10-15 15:39 ` Jens Axboe
2018-10-15 18:26   ` Paolo Valente
2018-10-15 19:26     ` Jens Axboe
2018-10-15 19:44       ` Paolo Valente
2018-10-16 17:35         ` Jens Axboe
2018-10-17 10:05           ` Jan Kara
2018-10-17 14:48             ` Bart Van Assche
2018-10-17 14:59               ` Bryan Gurney
2018-10-19  8:42                 ` Linus Walleij
2018-10-19 13:36                   ` Bryan Gurney
2018-10-19 13:44                     ` Johannes Thumshirn
2018-10-19 14:16                       ` Bryan Gurney
2018-10-22  8:12                   ` Jens Axboe [this message]
2018-10-17 16:01               ` Mark Brown
2018-10-17 16:29             ` Jens Axboe
2018-10-18  7:21               ` Jan Kara
2018-10-18 14:35                 ` Jens Axboe
2018-10-19  8:22                   ` Pavel Machek
2018-10-22  8:08                     ` Jens Axboe
2018-11-02 10:40           ` Oleksandr Natalenko
2018-10-19 10:59     ` Paolo Valente
2018-10-22  8:21       ` Jens Axboe
2018-10-16 13:42 ` Ulf Hansson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=eb60af4f-40bb-da3a-1399-60040d2d2fe2@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=Damien.LeMoal@wdc.com \
    --cc=adrian.hunter@intel.com \
    --cc=bgurney@redhat.com \
    --cc=broonie@kernel.org \
    --cc=bvanassche@acm.org \
    --cc=corbet@lwn.net \
    --cc=dedekind1@gmail.com \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=hch@infradead.org \
    --cc=jack@suse.cz \
    --cc=jthumshirn@suse.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=oleksandr@natalenko.name \
    --cc=paolo.valente@linaro.org \
    --cc=pavel@ucw.cz \
    --cc=richard@nod.at \
    --cc=ulf.hansson@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox