From: Ming Lei <ming.lei@redhat.com>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: Baolin Wang <baolin.wang7@gmail.com>,
Christoph Hellwig <hch@infradead.org>,
axboe@kernel.dk, Ulf Hansson <ulf.hansson@linaro.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Arnd Bergmann <arnd@arndb.de>,
Linus Walleij <linus.walleij@linaro.org>,
Paolo Valente <paolo.valente@linaro.org>,
Orson Zhai <orsonzhai@gmail.com>,
Chunyan Zhang <zhang.lyra@gmail.com>,
linux-mmc <linux-mmc@vger.kernel.org>,
linux-block <linux-block@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH v2 1/7] block: Extand commit_rqs() to do batch processing
Date: Tue, 12 May 2020 15:55:01 +0800 [thread overview]
Message-ID: <20200512075501.GF1531898@T590> (raw)
In-Reply-To: <9dc69d5a-b4f3-23a6-e033-377b4e133f97@grimberg.me>
On Mon, May 11, 2020 at 11:26:07PM -0700, Sagi Grimberg wrote:
>
> > > devices will benefit from the batching so maybe the flag needs to be
> > > inverted? BLK_MQ_F_DONT_BATCHING_SUBMISSION?
> >
> > Actually I'd rather to not add any flag, and we may use some algorithm
> > (maybe EWMA or other intelligent stuff, or use hctx->dispatch_busy directly)
> > to figure out one dynamic batching number which is used to dequeue requests
> > from scheduler or sw queue.
> >
> > Then just one single dispatch io code path is enough.
>
> Sounds good to me, do you plan to submit a patchset?
>
Yeah, I am working on that.
Thanks,
Ming
next prev parent reply other threads:[~2020-05-12 7:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-26 9:38 [RFC PATCH v2 0/7] Add MMC packed request support Baolin Wang
2020-04-26 9:38 ` [RFC PATCH v2 1/7] block: Extand commit_rqs() to do batch processing Baolin Wang
2020-04-27 15:46 ` Christoph Hellwig
2020-04-28 8:02 ` Baolin Wang
2020-05-08 21:35 ` Sagi Grimberg
2020-05-08 21:46 ` Ming Lei
2020-05-08 22:19 ` Sagi Grimberg
2020-05-08 23:22 ` Ming Lei
2020-05-09 8:57 ` Baolin Wang
2020-05-09 9:43 ` Ming Lei
2020-05-10 7:44 ` Sagi Grimberg
2020-05-11 1:29 ` Ming Lei
2020-05-11 9:23 ` Sagi Grimberg
2020-05-11 11:47 ` Ming Lei
2020-05-12 6:26 ` Sagi Grimberg
2020-05-12 7:55 ` Ming Lei [this message]
2020-04-26 9:38 ` [RFC PATCH v2 2/7] mmc: Add MMC packed request support for MMC software queue Baolin Wang
2020-04-26 9:38 ` [RFC PATCH v2 3/7] mmc: host: sdhci: Introduce ADMA3 transfer mode Baolin Wang
2020-04-26 9:38 ` [RFC PATCH v2 4/7] mmc: host: sdhci: Factor out the command configuration Baolin Wang
2020-04-26 9:38 ` [RFC PATCH v2 5/7] mmc: host: sdhci: Remove redundant sg_count member of struct sdhci_host Baolin Wang
2020-04-26 9:38 ` [RFC PATCH v2 6/7] mmc: host: sdhci: Add MMC packed request support Baolin Wang
2020-04-26 9:39 ` [RFC PATCH v2 7/7] mmc: host: sdhci-sprd: " Baolin Wang
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=20200512075501.GF1531898@T590 \
--to=ming.lei@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=baolin.wang7@gmail.com \
--cc=hch@infradead.org \
--cc=linus.walleij@linaro.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=orsonzhai@gmail.com \
--cc=paolo.valente@linaro.org \
--cc=sagi@grimberg.me \
--cc=ulf.hansson@linaro.org \
--cc=zhang.lyra@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).