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 <mwi...@suse.com>, Tel. +49 (0)911 74053 2107 SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg)
