From: Guixin Liu <kanie@linux.alibaba.com>
To: Christoph Hellwig <hch@lst.de>
Cc: kbusch@kernel.org, axboe@kernel.dk, sagi@grimberg.me,
kch@nvidia.com, linux-nvme@lists.infradead.org
Subject: Re: [PATCH v2] nvme-multipath: introduce service-time iopolicy
Date: Thu, 7 Nov 2024 15:09:33 +0800 [thread overview]
Message-ID: <19cf3e11-83d4-4057-a643-e052bab7680a@linux.alibaba.com> (raw)
In-Reply-To: <20241107063907.GA3353@lst.de>
在 2024/11/7 14:39, Christoph Hellwig 写道:
> On Thu, Nov 07, 2024 at 02:32:49PM +0800, Guixin Liu wrote:
>> The service-time policy can dispatch I/O to the path with the lowest
>> total amount of currently processed I/O, ensuring that new I/O can be
>> sent to less-loaded paths when some paths are overloaded, thereby
>> achieving lower latency.
> What is the exact use case for this? The commit log is unfortunately
> very sparse.
In scenarios with varying random I/O sizes, the different I/O sizes
being processed on
each path can lead to slower processing and higher latency on paths
under heavy load. By
distributing the I/O to other paths with lighter loads, the I/O can be
processed more
quickly.
Sorry for the sparse commit log, I will send a v3 to expain detaily.
> All these little policies add up, and we have absolutely
> no documentation on them :(
I'm glad to add a document to introduce all these nvme-multipath polices
within v3 patchset.
Best Regards,
Guixin Liu
prev parent reply other threads:[~2024-11-07 7:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 6:32 [PATCH v2] nvme-multipath: introduce service-time iopolicy Guixin Liu
2024-11-07 6:39 ` Christoph Hellwig
2024-11-07 7:09 ` Guixin Liu [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=19cf3e11-83d4-4057-a643-e052bab7680a@linux.alibaba.com \
--to=kanie@linux.alibaba.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.