public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Thumshirn <jthumshirn@suse.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: Alex Ivanov <yourbestfriend@openmailbox.org>,
	linux-block@vger.kernel.org
Subject: Re: [PATCH] elevator: allow specifying elevator by config boot param for blk-mq devices
Date: Fri, 14 Jul 2017 08:40:26 +0200	[thread overview]
Message-ID: <20170714064026.GB3484@linux-x5ow.site> (raw)
In-Reply-To: <49033d7d-8941-3c17-962f-dab170401bcf@kernel.dk>

On Thu, Jul 13, 2017 at 08:02:41AM -0600, Jens Axboe wrote:
> Because it sucks as an interface - there's no way to apply different
> settings to different devices, and using the kernel command line to
> control something like this is ugly. It never should have been done.
> 
> The sysfs interface, either manually, scripted, or through udev,
> makes a lot more sense.

Not that I disagree with your reasons, but not being able to select a
mq scheduler confuses quite some users out there.

Byte,
	Johannes
-- 
Johannes Thumshirn                                          Storage
jthumshirn@suse.de                                +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N�rnberg
GF: Felix Imend�rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N�rnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850

  parent reply	other threads:[~2017-07-14  6:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-12 18:57 [PATCH] elevator: allow specifying elevator by config boot param for blk-mq devices Alex Ivanov
2017-07-12 22:51 ` Jens Axboe
2017-07-13 10:11   ` Johannes Thumshirn
2017-07-13 14:02     ` Jens Axboe
2017-07-14  5:12       ` Paolo Valente
2017-07-14  6:40       ` Johannes Thumshirn [this message]
2017-07-14 14:26         ` Jens Axboe
2017-07-17  6:55           ` Johannes Thumshirn

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=20170714064026.GB3484@linux-x5ow.site \
    --to=jthumshirn@suse.de \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=yourbestfriend@openmailbox.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