From: Jens Axboe <axboe@kernel.dk>
To: Jianchao Wang <jianchao.w.wang@oracle.com>, osandov@osandov.com
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3 0/2] block: kyber: make kyber more friendly with merging
Date: Wed, 30 May 2018 10:48:50 -0600 [thread overview]
Message-ID: <3f44d1dc-6b81-9f51-9e2d-68f1faba1684@kernel.dk> (raw)
In-Reply-To: <1527665168-1965-1-git-send-email-jianchao.w.wang@oracle.com>
On 5/30/18 1:26 AM, Jianchao Wang wrote:
> Hi Jens
>
> This is the 3rd version patchset to make the kyber io scheduler more firendly
> with merging.
>
> Most of time, kyber io scheduler will not leave any requests in ctx rq_list,
> this is because even if tokens of one domain is used up, kyber will try to
> dispatch requests from other domain and flush the rq_list there. So there is not
> any change to do merge.
>
> To improve this, setup kyber_ctx_queue (kcq) which is similar with blk_mq_ctx but has
> rq_list for every domain, and build mapping between kcq and khd as ctx and hctx.
> Then we could merge, insert and dispatch on rq_list of different domains separately.
> At the same time, only flush the rq_list of kcq after get domain token
> successfully, then the requests could be left in the rq_list of that domain and
> maybe merged with following io. In my local test on NVMe card, the sequential io
> performance could be improved a lot, especially on high workload. More details
> please refer to the second patch.
Great work, thanks Jianchao - applied for 4.18.
--
Jens Axboe
prev parent reply other threads:[~2018-05-30 16:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 7:26 Jianchao Wang
2018-05-30 7:26 ` [PATCH V3 1/2] blk-mq: abstract out blk-mq-sched rq list iteration bio merge helper Jianchao Wang
2018-05-30 7:26 ` [PATCH V3 2/2] block: kyber: make kyber more friendly with merging Jianchao Wang
2018-05-30 16:40 ` Omar Sandoval
2018-05-30 16:48 ` Jens Axboe [this message]
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=3f44d1dc-6b81-9f51-9e2d-68f1faba1684@kernel.dk \
--to=axboe@kernel.dk \
--cc=jianchao.w.wang@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=osandov@osandov.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
Powered by JetHome