[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DM5PR04MB1085F5C71B915665133D2E3FFC780@DM5PR04MB1085.namprd04.prod.outlook.com>
Date: Wed, 27 Sep 2017 12:58:53 +0000
From: Avri Altman <Avri.Altman@....com>
To: Linus Walleij <linus.walleij@...aro.org>,
Adrian Hunter <adrian.hunter@...el.com>
CC: Ulf Hansson <ulf.hansson@...aro.org>,
linux-mmc <linux-mmc@...r.kernel.org>,
linux-block <linux-block@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Bough Chen <haibo.chen@....com>,
Alex Lemberg <Alex.Lemberg@....com>,
Mateusz Nowak <mateusz.nowak@...el.com>,
Yuliy Izrailov <Yuliy.Izrailov@....com>,
Jaehoon Chung <jh80.chung@...sung.com>,
Dong Aisheng <dongas86@...il.com>,
Das Asutosh <asutoshd@...eaurora.org>,
Zhangfei Gao <zhangfei.gao@...il.com>,
Sahitya Tummala <stummala@...eaurora.org>,
Harjani Ritesh <riteshh@...eaurora.org>,
Venu Byravarasu <vbyravarasu@...dia.com>,
Shawn Lin <shawn.lin@...k-chips.com>,
Christoph Hellwig <hch@....de>
Subject: RE: [PATCH V9 09/15] mmc: core: Add parameter use_blk_mq
> -----Original Message-----
> From: linux-mmc-owner@...r.kernel.org [mailto:linux-mmc-
> owner@...r.kernel.org] On Behalf Of Linus Walleij
> Sent: Wednesday, September 27, 2017 2:42 AM
> To: Adrian Hunter <adrian.hunter@...el.com>
> Cc: Ulf Hansson <ulf.hansson@...aro.org>; linux-mmc <linux-
> mmc@...r.kernel.org>; linux-block <linux-block@...r.kernel.org>; linux-
> kernel <linux-kernel@...r.kernel.org>; Bough Chen <haibo.chen@....com>;
> Alex Lemberg <Alex.Lemberg@....com>; Mateusz Nowak
> <mateusz.nowak@...el.com>; Yuliy Izrailov <Yuliy.Izrailov@....com>;
> Jaehoon Chung <jh80.chung@...sung.com>; Dong Aisheng
> <dongas86@...il.com>; Das Asutosh <asutoshd@...eaurora.org>; Zhangfei
> Gao <zhangfei.gao@...il.com>; Sahitya Tummala
> <stummala@...eaurora.org>; Harjani Ritesh <riteshh@...eaurora.org>;
> Venu Byravarasu <vbyravarasu@...dia.com>; Shawn Lin <shawn.lin@...k-
> chips.com>; Christoph Hellwig <hch@....de>
> Subject: Re: [PATCH V9 09/15] mmc: core: Add parameter use_blk_mq
>
> On Fri, Sep 22, 2017 at 2:36 PM, Adrian Hunter <adrian.hunter@...el.com>
> 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@...el.com>
>
> > +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 majordomo@...r.kernel.org More majordomo info at
> http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists