From: Talker Alex <alextalker@yandex.ru>
To: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: NVMeoF driver & Reservations
Date: Tue, 03 Dec 2019 11:51:36 +0300 [thread overview]
Message-ID: <11467571575363096@myt3-605d5ea4bc20.qloud-c.yandex.net> (raw)
In-Reply-To: <BYAPR04MB5749D5699EB15878C41F4BA386430@BYAPR04MB5749.namprd04.prod.outlook.com>
> But if you have a legit scenario or a
> use-case I'll be happy to work on this.
I think in SCSI subsystems this support is usually made to pass-by Microsoft Windows Server Failover Clustering requirements.
Regarding the use-case I think this is as usual an effort to create
a lock mechanism in order to synchronize access to the same device without an additional layer on client side.
I don't know whether NVMeoF works on Windows at all by now, haven't checked yet.
Anyway, I'd like to see your code if you published it anywhere.
Unlikely with SCSI, NVMe Reservations seems to be easier to implement with dedicated HostNQN identifier,
digging through the specification conditions.
------------------
Best regards,
Alex
_______________________________________________
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 8:51 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 [this message]
2019-12-03 16:08 ` Bart Van Assche
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=11467571575363096@myt3-605d5ea4bc20.qloud-c.yandex.net \
--to=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).