Linux-NVME Archive on lore.kernel.org
 help / color / Atom feed
From: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: 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 19:54:23 +0000
Message-ID: <784A9299-C11B-406C-838E-8785BEAB6637@wdc.com> (raw)
In-Reply-To: <962eea1d-e89d-45dc-9b3c-6a4606927a0b@acm.org>

Indeed I have looked into this and it's very helpful. 
Thanks for reminding me again :). 
> On Dec 3, 2019, at 8:08 AM, Bart Van Assche <bvanassche@acm.org> wrote:
> 
> 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

      reply index

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 ` Talker Alex
2019-12-02 22:07   ` Chaitanya Kulkarni
2019-12-03  8:51     ` Talker Alex
2019-12-03 16:08     ` Bart Van Assche
2019-12-03 19:54       ` Chaitanya Kulkarni [this message]

Reply instructions:

You may reply publically 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=784A9299-C11B-406C-838E-8785BEAB6637@wdc.com \
    --to=chaitanya.kulkarni@wdc.com \
    --cc=alextalker@yandex.ru \
    --cc=bvanassche@acm.org \
    --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

Linux-NVME Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-nvme/0 linux-nvme/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-nvme linux-nvme/ https://lore.kernel.org/linux-nvme \
		linux-nvme@lists.infradead.org
	public-inbox-index linux-nvme

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.infradead.lists.linux-nvme


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git