From: Hannes Reinecke <hare@suse.de>
To: Guixin Liu <kanie@linux.alibaba.com>,
Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
onathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>
Cc: linux-nvme@lists.infradead.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH 0/2] nvme: Introduce service-time iopolicy
Date: Wed, 1 Jul 2026 13:14:13 +0200 [thread overview]
Message-ID: <8103a626-d07b-4b20-b10e-d258485176ee@suse.de> (raw)
In-Reply-To: <20260617114602.2224074-1-kanie@linux.alibaba.com>
On 6/17/26 1:45 PM, Guixin Liu wrote:
> Hi all,
> I developed the service-time iopolicy in nvme native
> multipath, please review, all comments are wellcome.
>
> Guixin Liu (2):
> nvme-multipath: add service-time I/O policy
> docs: nvme-multipath: document service-time I/O policy
>
> Documentation/admin-guide/nvme-multipath.rst | 31 +++-
> drivers/nvme/host/multipath.c | 165 ++++++++++++++++++-
> drivers/nvme/host/nvme.h | 6 +
> drivers/nvme/host/sysfs.c | 5 +-
> 4 files changed, 202 insertions(+), 5 deletions(-)
>
We're still waiting for the adaptive I/O policy to be included, so I
guess this patch should build on top of that.
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Frankenstr. 146, 90461 Nürnberg
HRB 36809 (AG Nürnberg), GF: I. Totev, A. McDonald, W. Knoblich
next prev parent reply other threads:[~2026-07-01 11:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 11:45 [PATCH 0/2] nvme: Introduce service-time iopolicy Guixin Liu
2026-06-17 11:45 ` [PATCH 1/2] nvme-multipath: add service-time I/O policy Guixin Liu
2026-06-17 11:45 ` [PATCH 2/2] docs: nvme-multipath: document " Guixin Liu
2026-07-01 11:14 ` Hannes Reinecke [this message]
2026-07-02 2:34 ` [PATCH 0/2] nvme: Introduce service-time iopolicy Guixin Liu
2026-07-14 7:01 ` Guixin Liu
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=8103a626-d07b-4b20-b10e-d258485176ee@suse.de \
--to=hare@suse.de \
--cc=axboe@kernel.dk \
--cc=corbet@lwn.net \
--cc=hch@lst.de \
--cc=kanie@linux.alibaba.com \
--cc=kbusch@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=skhan@linuxfoundation.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