On Fri, Sep 22, 2017 at 2:36 PM, Adrian Hunter <adrian.hunter@xxxxxxxxx> 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 <adrian.hunter@xxxxxxxxx> > +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? 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
