From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@infradead.org>
Cc: Jeff Moyer <jmoyer@redhat.com>,
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: Wed, 30 May 2018 08:22:40 -0600 [thread overview]
Message-ID: <71ad1d2e-b4cc-a36d-22ea-86574c76370c@kernel.dk> (raw)
In-Reply-To: <20180530084928.GB29413@infradead.org>
On 5/30/18 2:49 AM, Christoph Hellwig wrote:
> While I really don't want drivers to change the I/O schedule themselves
> we have a class of devices (zoned) that don't work at all with certain
> I/O schedulers. The kernel not chosing something sane and requiring
> user workarounds is just silly.
They work just fine for probing and reading purposes. There's absolutely
no reason why we can't handle these special snowflakes with a udev rule.
--
Jens Axboe
next prev parent reply other threads:[~2018-05-30 14:22 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
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 [this message]
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=71ad1d2e-b4cc-a36d-22ea-86574c76370c@kernel.dk \
--to=axboe@kernel.dk \
--cc=Damien.LeMoal@wdc.com \
--cc=bgurney@redhat.com \
--cc=hch@infradead.org \
--cc=jmoyer@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.