All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Wilck <mwilck@suse.com>
To: Bart Van Assche <Bart.VanAssche@wdc.com>,
	"hch@lst.de" <hch@lst.de>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] scsi: default to scsi-mq
Date: Mon, 26 Jun 2017 20:55:49 +0200	[thread overview]
Message-ID: <1498503349.27347.15.camel@suse.com> (raw)
In-Reply-To: <1498491078.8799.2.camel@wdc.com>

Hi Bart,

On Mon, 2017-06-26 at 15:31 +0000, Bart Van Assche wrote:
> On Mon, 2017-06-26 at 12:13 +0000, Bart Van Assche wrote:
> > On Thu, 2017-06-22 at 17:05 +0200, Martin Wilck wrote:
> > > On Fri, 2017-06-16 at 10:27 +0200, Christoph Hellwig wrote:
> > > > Remove the SCSI_MQ_DEFAULT config option and default to the
> > > > blk-mq
> > > > I/O
> > > > path now that we had plenty of testing, and have I/O schedulers
> > > > for
> > > > blk-mq.  The module option to disable the blk-mq path is kept
> > > > around
> > > > for now.
> > > 
> > > Could you explain why you remove the option entirely rather than
> > > just
> > > changing the default? Some distributions may wish to keep the
> > > ability
> > > to choose the compiled-in default.
> > 
> > Hello Martin,
> > 
> > Would it work for you to keep this patch as a distro-private patch?
> 
> What I meant is: apply this patch to the upstream kernel and keep 
> CONFIG_SCSI_MQ_DEFAULT as a distro-private patch.

First, let me clarify that I was not speaking for SUSE when I asked
this question, just expressing my personal concerns, partly motivated
by my previous employment at a hardware manufacturer.

Of course distro-makers can deal with this in various ways, for example
the way you suggest, although that sounds like a rather painful route
to choose.

I personally find it odd that the compile-time choice goes away while
the run-time choice remains available. I understand what Christoph is
trying to achieve, but if it was up to me, I'd prefer to change the
default and mark the "n" setting as deprecated.

Again, please do not take this as an official SUSE statement. I just
happen to be subscribed to linux-scsi with my suse.com address.

Regards,
Martin

-- 
Dr. Martin Wilck <mwilck@suse.com>, Tel. +49 (0)911 74053 2107
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)

  reply	other threads:[~2017-06-26 18:56 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-16  8:27 [PATCH] scsi: default to scsi-mq Christoph Hellwig
2017-06-19  6:03 ` [lkp-robot] [scsi] ebc76736f2: fio.write_bw_MBps -4% regression kernel test robot
2017-06-19  6:03   ` kernel test robot
2017-06-19  7:09   ` Christoph Hellwig
2017-06-19  7:09     ` Christoph Hellwig
2017-06-19  7:09     ` Christoph Hellwig
2017-06-19  7:49     ` Ye Xiaolong
2017-06-19  7:49       ` Ye Xiaolong
2017-06-19  7:49       ` Ye Xiaolong
2017-06-19  8:41       ` Christoph Hellwig
2017-06-19  8:41         ` Christoph Hellwig
2017-06-19  8:52         ` Ye Xiaolong
2017-06-19  8:52           ` Ye Xiaolong
2017-06-19  9:39           ` Christoph Hellwig
2017-06-19  9:39             ` Christoph Hellwig
2017-06-20  2:16             ` Ye Xiaolong
2017-06-20  2:16               ` Ye Xiaolong
2017-06-20  6:04               ` Christoph Hellwig
2017-06-20  6:04                 ` Christoph Hellwig
2017-06-22 15:05 ` [PATCH] scsi: default to scsi-mq Martin Wilck
2017-06-26  9:48   ` Christoph Hellwig
2017-06-26 12:13   ` Bart Van Assche
2017-06-26 15:31     ` Bart Van Assche
2017-06-26 18:55       ` Martin Wilck [this message]
2017-06-27  6:07         ` Bart Van Assche
2017-07-10 15:50 ` Bart Van Assche
2017-07-11 10:22   ` John Garry
2017-07-11 13:32     ` Bart Van Assche
2017-07-11 14:14       ` John Garry
2017-07-11 15:46         ` Bart Van Assche
2017-07-11 17:34           ` John Garry
2017-07-12  8:26             ` John Garry
2017-07-12 14:18               ` Bart Van Assche
2017-07-12 15:54                 ` Jonathan Cameron
2017-07-14  9:56                   ` Jonathan Cameron
2017-07-14 12:45                     ` hch
2017-07-18 15:58                       ` Jonathan Cameron
2017-07-18 16:24                         ` Jonathan Cameron

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=1498503349.27347.15.camel@suse.com \
    --to=mwilck@suse.com \
    --cc=Bart.VanAssche@wdc.com \
    --cc=hch@lst.de \
    --cc=linux-scsi@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.