Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Guixin Liu <kanie@linux.alibaba.com>
To: Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
	Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>
Cc: linux-nvme@lists.infradead.org
Subject: Re: [PATCH v3 0/2] Introduce service-time multipath policy and document
Date: Wed, 13 Nov 2024 18:22:05 +0800	[thread overview]
Message-ID: <fc116473-340a-48e2-8bfa-79cd5e318e73@linux.alibaba.com> (raw)
In-Reply-To: <20241108085449.49972-1-kanie@linux.alibaba.com>

Hi Christoph,

     Could you please take a look on this patchset?

Best Regards,

Guixin Liu

在 2024/11/8 16:54, Guixin Liu 写道:
> Hi,
>    This patchset introduce a new multipath policy, service-time, and also
> add a new document to introduce nvme-multipath and all policies supported.
>
> Changes from v2 to v3:
> - Add more detail to message body(Christoph).
> - Add a document to introduce nvme-multipath and all policies supported.
>
> Changes from v1 to v2:
> - Use atomic64_t to replace atomic_t (Keith).
>
> Guixin Liu (2):
>    nvme-multipath: introduce service-time iopolicy
>    docs, nvme: add a nvme-multipath document
>
>   Documentation/nvme/nvme-multipath.rst | 83 +++++++++++++++++++++++++++
>   drivers/nvme/host/multipath.c         | 53 ++++++++++++++++-
>   drivers/nvme/host/nvme.h              |  3 +
>   3 files changed, 138 insertions(+), 1 deletion(-)
>   create mode 100644 Documentation/nvme/nvme-multipath.rst
>


      parent reply	other threads:[~2024-11-13 10:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-08  8:54 [PATCH v3 0/2] Introduce service-time multipath policy and document Guixin Liu
2024-11-08  8:54 ` [PATCH v3 1/2] nvme-multipath: introduce service-time iopolicy Guixin Liu
2024-11-08  8:54 ` [PATCH v3 2/2] docs, nvme: add a nvme-multipath document Guixin Liu
2024-11-11 10:41 ` [PATCH v3 0/2] Introduce service-time multipath policy and document Guixin Liu
2024-11-13 10:22 ` 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=fc116473-340a-48e2-8bfa-79cd5e318e73@linux.alibaba.com \
    --to=kanie@linux.alibaba.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox