> -----Original Message----- > From: [email protected] [mailto:linux-mmc- > [email protected]] On Behalf Of Linus Walleij > Sent: Wednesday, September 27, 2017 2:42 AM > To: Adrian Hunter <[email protected]> > Cc: Ulf Hansson <[email protected]>; linux-mmc <linux- > [email protected]>; linux-block <[email protected]>; linux- > kernel <[email protected]>; Bough Chen <[email protected]>; > Alex Lemberg <[email protected]>; Mateusz Nowak > <[email protected]>; Yuliy Izrailov <[email protected]>; > Jaehoon Chung <[email protected]>; Dong Aisheng > <[email protected]>; Das Asutosh <[email protected]>; Zhangfei > Gao <[email protected]>; Sahitya Tummala > <[email protected]>; Harjani Ritesh <[email protected]>; > Venu Byravarasu <[email protected]>; Shawn Lin <shawn.lin@rock- > chips.com>; Christoph Hellwig <[email protected]> > Subject: Re: [PATCH V9 09/15] mmc: core: Add parameter use_blk_mq > > On Fri, Sep 22, 2017 at 2:36 PM, Adrian Hunter <[email protected]> > wrote: > > > Until mmc has blk-mq support fully implemented and tested, add a > > parameter use_blk_mq, default to false unless config option > > MMC_MQ_DEFAULT is selected. > > > > Signed-off-by: Adrian Hunter <[email protected]> > > > +config MMC_MQ_DEFAULT > > + bool "MMC: use blk-mq I/O path by default" > > + depends on MMC && BLOCK > > I would say: > default y > > Why not. SCSI is starting to enable this by default so IMO we should not take > the intermediate step of having this as optional. Otherwise it never gets > tested. > > Set it to default y and after two kernel releases, if nothing happens, we > simply > delete the old block layer path. > > > +#ifdef CONFIG_MMC_MQ_DEFAULT > > +bool mmc_use_blk_mq = true; > > +#else > > +bool mmc_use_blk_mq = false; > > +#endif > > +module_param_named(use_blk_mq, mmc_use_blk_mq, bool, S_IWUSR | > > +S_IRUGO); > > Are people really modprobing this so it needs to be a module parameter?
Module param can be changed in runtime > > Maybe I'm the only developer stupid enough to just recompile and reboot the > whole kernel, I guess this makes sense if you're testing on the same machine > you're developing on (no cross-compilation and remote target) which I guess > is what some Intel people are doing with their laptops. > > Yours, > Linus Walleij > -- > To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the > body of a message to [email protected] More majordomo info at > http://vger.kernel.org/majordomo-info.html
