From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH] nvme: Add weighted-round-robin arbitration support
Date: Tue, 9 Jan 2018 10:05:39 -0700 [thread overview]
Message-ID: <20180109170539.GE15154@localhost.localdomain> (raw)
In-Reply-To: <ec6f0d2f-2751-0a29-7762-7a32830e0fcc@samsung.com>
On Tue, Jan 09, 2018@07:20:58PM +0530, Kanchan Joshi wrote:
> It seems to me that some sort of differentiation (among tasks of various
> classes) during tag allocation is required to handle this. Perhaps, static
> division of available tags into 4 priority classes needs to be done in block
> layer.
Yes, I was thinking either some kind priorty based tag reservation, or
possibly entirely different hctx's for each priority. The block layer
currently doesn't provide this kind of separation, but it was mentioned
the latter might be appropriate for hipri/polled IO, so maybe that idea
can extend to WRR.
next prev parent reply other threads:[~2018-01-09 17:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180104150334epcas1p14579a6ab7bcf1b6ce326d0bce89c91e1@epcas1p1.samsung.com>
2018-01-04 15:02 ` [PATCH] nvme: Add weighted-round-robin arbitration support Kanchan Joshi
2018-01-04 17:38 ` Keith Busch
2018-01-09 13:50 ` Kanchan Joshi
2018-01-09 17:05 ` Keith Busch [this message]
2018-01-10 15:27 ` Kanchan Joshi
2018-01-10 23:57 ` Keith Busch
2018-01-14 9:56 ` Sagi Grimberg
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=20180109170539.GE15154@localhost.localdomain \
--to=keith.busch@intel.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