From: Christoph Hellwig <hch@lst.de>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>,
kbusch@kernel.org, sagi@grimberg.me,
linux-nvme@lists.infradead.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] nvme: implement ->get_unique_id
Date: Fri, 5 Jul 2024 19:32:16 +0200 [thread overview]
Message-ID: <20240705173216.GA2279@lst.de> (raw)
In-Reply-To: <ZogqNFka2384O0pT@tissot.1015granger.net>
On Fri, Jul 05, 2024 at 01:15:32PM -0400, Chuck Lever wrote:
> I will connect with you offline to advise me on setting up a test
> harness similar to what I have with iSCSI.
Unfortunately there is nothing that works out of the box right now.
What I've done is that I've taken this patch:
https://lore.kernel.org/linux-nvme/20240229031241.8692-1-kanie@linux.alibaba.com/
which still needs to address a few issues before we can merge it,
and then hacke the nvmet code to not autogenerate a UUID.
I'm looking into a patch to disable uuid autogeneration, and hopefully
we can upstream the persistent reservation support for 6.12. After
that it should be very similar to the iSCSI test setup.
next prev parent reply other threads:[~2024-07-05 17:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 16:46 [PATCH] nvme: implement ->get_unique_id Christoph Hellwig
2024-07-05 17:15 ` Chuck Lever
2024-07-05 17:32 ` Christoph Hellwig [this message]
2024-07-06 21:38 ` Sagi Grimberg
2024-07-08 17:50 ` Keith Busch
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=20240705173216.GA2279@lst.de \
--to=hch@lst.de \
--cc=chuck.lever@oracle.com \
--cc=kbusch@kernel.org \
--cc=linux-nfs@vger.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