From: Guixin Liu <kanie@linux.alibaba.com>
To: Hannes Reinecke <hare@suse.de>, 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: Thu, 2 Jul 2026 10:34:46 +0800 [thread overview]
Message-ID: <2dc374ad-b365-48c0-8d45-aacf53f80e4c@linux.alibaba.com> (raw)
In-Reply-To: <8103a626-d07b-4b20-b10e-d258485176ee@suse.de>
在 2026/7/1 19:14, Hannes Reinecke 写道:
> 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
Yes, I work on that adaptation. But I thought it would be helpful
for the maintainers to review the logic here first before I proceed.
Best Regards,
Guixin Liu
next prev parent reply other threads:[~2026-07-02 2:34 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 ` [PATCH 0/2] nvme: Introduce service-time iopolicy Hannes Reinecke
2026-07-02 2:34 ` Guixin Liu [this message]
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=2dc374ad-b365-48c0-8d45-aacf53f80e4c@linux.alibaba.com \
--to=kanie@linux.alibaba.com \
--cc=axboe@kernel.dk \
--cc=corbet@lwn.net \
--cc=hare@suse.de \
--cc=hch@lst.de \
--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