From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Guixin Liu <kanie@linux.alibaba.com>
Cc: "hch@lst.de" <hch@lst.de>, "sagi@grimberg.me" <sagi@grimberg.me>,
Chaitanya Kulkarni <chaitanyak@nvidia.com>,
Keith Busch <kbusch@kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH] nvmet: support reservation feature
Date: Wed, 10 Jan 2024 04:36:57 +0000 [thread overview]
Message-ID: <a1e024e0-5218-4f94-ae31-05ba30bf77a9@nvidia.com> (raw)
In-Reply-To: <a56b996e-8d38-42e9-914c-8877182c5cc0@linux.alibaba.com>
On 1/9/24 19:19, Guixin Liu wrote:
>
> 在 2024/1/10 01:01, Keith Busch 写道:
>> On Tue, Jan 09, 2024 at 08:10:08PM +0800, Guixin Liu wrote:
>>> This patch implements the reservation feature, includes:
>>> 1. reservation register(register, unregister and replace).
>>> 2. reservation acquire(acquire, preempt, preempt and abort).
>>> 3. reservation release(release and clear).
>>> 4. reservation report.
>>>
>>> And also make reservation configurable, one can set ns to support
>>> reservation before enable ns. The default of resv_enable is false.
>>>
>>> Signed-off-by: Guixin Liu<kanie@linux.alibaba.com>
>>> ---
>>> Hi guys,
>>> I've implemented the NVMe reservation feature. Please review
>>> it, all
>>> comments are welcome.
>> Why? If you have a real use case, let's add a blktest example added to
>> that project.
> OK, I will research the blktests, and add some tests.
Here is it :- https://github.com/osandov/blktests
Please CC me and Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
when you send tests.
-ck
next prev parent reply other threads:[~2024-01-10 4:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 12:10 [PATCH] nvmet: support reservation feature Guixin Liu
2024-01-09 17:01 ` Keith Busch
2024-01-10 3:19 ` Guixin Liu
2024-01-10 4:36 ` Chaitanya Kulkarni [this message]
2024-01-10 5:59 ` Guixin Liu
2024-01-10 17:57 ` Keith Busch
2024-01-10 4:34 ` Chaitanya Kulkarni
2024-01-10 5:58 ` Guixin Liu
2024-01-10 8:31 ` Chaitanya Kulkarni
2024-01-10 8:45 ` Guixin Liu
2024-01-10 17:16 ` Jens Axboe
2024-01-10 15:47 ` Sagi Grimberg
[not found] ` <d9cf6a40-e0bc-4b2c-b421-b313e1f57f10@linux.alibaba.com>
2024-01-11 12:09 ` 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=a1e024e0-5218-4f94-ae31-05ba30bf77a9@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=hch@lst.de \
--cc=kanie@linux.alibaba.com \
--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