From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH RFC 0/4] nvmet: add support for port based io priority
Date: Mon, 20 May 2019 23:56:02 -0700 [thread overview]
Message-ID: <20190521065602.GA17946@infradead.org> (raw)
In-Reply-To: <SN6PR04MB4527B78B40C2B1D11355FA9F860B0@SN6PR04MB4527.namprd04.prod.outlook.com>
On Fri, May 17, 2019@04:28:43PM +0000, Chaitanya Kulkarni wrote:
> Okay, thanks for the reply Christoph. Quick question, when you mention
>
> "Until NVMe has an actually working priority" -> host side support for
>
> priority based block layer request -> NVMe Request processing with
>
> having weighted round robin priority SQ for NVMe Host ?
Weighted round robing is _NOT_ and I/O priority - it just just changes
arbitration. But there had been priority proposals in the working
group before, without much progress at the moment, though.
next prev parent reply other threads:[~2019-05-21 6:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 3:21 [PATCH RFC 0/4] nvmet: add support for port based io priority Chaitanya Kulkarni
2019-05-16 3:21 ` [RFC PATCH 1/4] nvmet: add iopriority definitions for port Chaitanya Kulkarni
2019-05-16 3:21 ` [PATCH] nvmet: get rid of extra line in the tcp code Chaitanya Kulkarni
2019-05-16 3:22 ` Chaitanya Kulkarni
2019-05-16 3:21 ` [RFC PATCH 2/4] nvmet: allow user to specify ioprioty from cfgfs Chaitanya Kulkarni
2019-05-16 3:21 ` [RFC PATCH 3/4] nvmet: set iopriority for each bio Chaitanya Kulkarni
2019-05-16 3:21 ` [RFC PATCH 4/4] nvmet: set iopriority for each kiocb for file Chaitanya Kulkarni
2019-05-16 7:32 ` Johannes Thumshirn
2019-05-17 9:45 ` [PATCH RFC 0/4] nvmet: add support for port based io priority Christoph Hellwig
2019-05-17 16:28 ` Chaitanya Kulkarni
2019-05-21 6:56 ` Christoph Hellwig [this message]
2019-05-24 8:08 ` 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=20190521065602.GA17946@infradead.org \
--to=hch@infradead.org \
/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