From: Bart Van Assche <bvanassche@acm.org>
To: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>,
Talker Alex <alextalker@yandex.ru>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: NVMeoF driver & Reservations
Date: Tue, 3 Dec 2019 08:08:18 -0800 [thread overview]
Message-ID: <962eea1d-e89d-45dc-9b3c-6a4606927a0b@acm.org> (raw)
In-Reply-To: <BYAPR04MB5749D5699EB15878C41F4BA386430@BYAPR04MB5749.namprd04.prod.outlook.com>
On 12/2/19 2:07 PM, Chaitanya Kulkarni wrote:
> On 12/01/2019 02:19 AM, Talker Alex wrote:
>> Hi!
>>
>> Is there plans to implement Reservations support in target driver(from NVMe v1.4 part 8.8)?
>> I see that host support is already implemented in nvme utility & driver level.
>> However, I haven't found hardware on which it works - target driver doesn't support this command and PCIe drives available to me also.
>>
>> So, I'm wondering if anyone begin to implement this feature at least on single target level.
>
> Yes there is and I also have testcases to test this feature from host side.
>
> for target I did start working on this but stopped it since I didn't
> find proper use-case (or a client) for it to justify the effort and
> code getting into kernel. But if you have a legit scenario or a
> use-case I'll be happy to work on this.
Hi Chaitanya,
If you would be considering to develop test code for NVMe reservations,
you may want to have a look at the SCSI persistent reservation tests in
the libiscsi test-tool
(https://github.com/sahlberg/libiscsi/tree/master/test-tool).
Bart.
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2019-12-03 16:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <92087051575042507@sas2-7fadb031fd9b.qloud-c.yandex.net>
2019-11-29 15:50 ` NVMeoF driver & Reservations Talker Alex
2019-12-02 22:07 ` Chaitanya Kulkarni
2019-12-03 8:51 ` Talker Alex
2019-12-03 16:08 ` Bart Van Assche [this message]
2019-12-03 19:54 ` Chaitanya Kulkarni
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=962eea1d-e89d-45dc-9b3c-6a4606927a0b@acm.org \
--to=bvanassche@acm.org \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=alextalker@yandex.ru \
--cc=linux-nvme@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).