From: Jeff Moyer <jmoyer@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Damien.LeMoal@wdc.com, linux-block@vger.kernel.org, bgurney@redhat.com
Subject: Re: [PATCH 0/2][RFC] block: default to deadline for SMR devices
Date: Fri, 25 May 2018 18:18:36 -0400 [thread overview]
Message-ID: <x49tvqvz8eb.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <9756f816-cea7-52cc-e616-54cd7b7d8c75@kernel.dk> (Jens Axboe's message of "Fri, 25 May 2018 16:04:09 -0600")
Hi, Jens,
Jens Axboe <axboe@kernel.dk> writes:
> On 5/25/18 3:14 PM, Jeff Moyer wrote:
>> Bryan Gurney reported I/O errors when using dm-zoned with a host-managed
>> SMR device. It turns out he was using CFQ, which is the default.
>> Unfortunately, as of v4.16, only the deadline schedulers work well with
>> host-managed SMR devices. This series aatempts to switch the elevator
>> to deadline for those devices.
>>
>> NOTE: I'm not super happy with setting up one iosched and then
>> immediately tearing it down. I'm open to suggestions on better ways
>> to accomplish this goal.
>
> Let's please not do this, a few years ago I finally managed to kill
> drivers changing the scheduler manually. Why can't this go into a
> udev (or similar) rule? That's where it belongs, imho.
We could do that. The downside is that distros will have to pick up
udev rules, which they haven't done yet, and the udev rules will have to
be kernel version dependent. And then later, when this restriction is
lifted, we'll have to update the udev rules. That also sounds awful to
me.
I understand why you don't like this patch set, but I happen to think
the alternative is worse. FYI, in Bryan's case, his system actually got
bricked (likely due to buggy firmware).
Ultimately, it's your call of course.
Cheers,
Jeff
next prev parent reply other threads:[~2018-05-25 22:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 21:14 [PATCH 0/2][RFC] block: default to deadline for SMR devices Jeff Moyer
2018-05-25 21:14 ` [PATCH 1/2] block: __elevator_change: add try_loading parameter Jeff Moyer
2018-05-25 21:14 ` [PATCH 2/2] block: default to deadline for host-managed SMR devices Jeff Moyer
2018-05-25 22:04 ` [PATCH 0/2][RFC] block: default to deadline for " Jens Axboe
2018-05-25 22:18 ` Jeff Moyer [this message]
2018-05-26 4:01 ` Jens Axboe
2018-05-29 12:14 ` Bryan Gurney
2018-05-30 6:22 ` Damien Le Moal
2018-05-30 8:47 ` Christoph Hellwig
2018-05-31 5:36 ` Damien Le Moal
2018-05-30 13:45 ` Bryan Gurney
2018-05-30 8:49 ` Christoph Hellwig
2018-05-30 14:22 ` Jens Axboe
2018-05-30 15:06 ` Jeff Moyer
2018-05-30 15:17 ` Jens Axboe
2018-05-30 15:45 ` Jeff Moyer
2018-05-30 15:52 ` Jens Axboe
2018-05-31 3:16 ` Damien Le Moal
2018-05-31 3:04 ` Damien Le Moal
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=x49tvqvz8eb.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=Damien.LeMoal@wdc.com \
--cc=axboe@kernel.dk \
--cc=bgurney@redhat.com \
--cc=linux-block@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).