From: Guixin Liu <kanie@linux.alibaba.com>
To: Daniel Wagner <dwagner@suse.de>
Cc: Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Chaitanya Kulkarni <kch@nvidia.com>,
Hannes Reinecke <hare@suse.com>,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH 0/2] nvmet: add namespace-level debugfs for reservation state
Date: Mon, 6 Jul 2026 11:10:41 +0800 [thread overview]
Message-ID: <1b56186c-9e5b-4e9a-813e-74e4d1511738@linux.alibaba.com> (raw)
In-Reply-To: <f0c00d47-0f33-4c9a-84ea-2fb82cd4d102@linux.alibaba.com>
在 2026/6/25 17:10, Guixin Liu 写道:
>
>
> 在 2026/6/25 15:17, Daniel Wagner 写道:
>> On Mon, Jun 22, 2026 at 06:44:16PM +0800, Guixin Liu wrote:
>>> This series adds debugfs support for inspecting NVMe target reservation
>>> (PR) state at the namespace level.
>>>
>>> Patch 1 introduces per-namespace debugfs directories under each
>>> subsystem,
>>> providing the infrastructure for namespace-specific debug entries.
>>>
>>> Patch 2 adds a 'reservation' file that exposes the persistent
>>> reservation
>>> state including enable status, generation counter, holder
>>> information, and
>>> the full registrant list.
>>>
>>> Example output with two registered hosts and an active holder:
>>>
>>> $ cat /sys/kernel/debug/nvmet/testnqn/ns1/reservation
>>> enable : 1
>>> generation : 2
>>> notify_mask : 0x0
>>> rtype : write_exclusive
>>> holder : hostid=11111111-1111-1111-1111-111111111111, rkey=0x1111
>>> registrants:
>>> hostid=11111111-1111-1111-1111-111111111111, rkey=0x1111
>>> hostid=22222222-2222-2222-2222-222222222222, rkey=0x2222
>> I expect blktests will make use of this interface eventually. The parser
>> for this wont be dead simple, sure doable but not simple. If you see a
>> way to make a bit simpler I wouldn't mind.
> How about this:
>
> 1. One holer, multi registrants:
> enable=1
> generation=2
> notify_mask=0x0
> rtype=write_exclusive
> holder=11111111-1111-1111-1111-111111111111,0x1111
> reg=11111111-1111-1111-1111-111111111111,0x1111
> reg=22222222-2222-2222-2222-222222222222,0x2222
>
> 2. No holder, multi registrants:
> enable=1
> generation=1
> notify_mask=0x0
> rtype=none
> holder=none
> reg=11111111-1111-1111-1111-111111111111,0x1111
> reg=22222222-2222-2222-2222-222222222222,0x2222
>
> 3. No registrant:
> enable=1
> generation=0
> notify_mask=0x0
> rtype=none
> holder=none
>
> 4. Reservation not enabled:
> enable=0
>
> Otherwise, the notify_mask can be stringization:
>
> notify_mask=reg_preempted,resv_released,resv_preempted
>
> Best Regards,
> Guixin Liu
>
Hi Daniel,
What do you think?
Best Regards,
Guixin Liu
next prev parent reply other threads:[~2026-07-06 3:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 10:44 [PATCH 0/2] nvmet: add namespace-level debugfs for reservation state Guixin Liu
2026-06-22 10:44 ` [PATCH 1/2] nvmet: add namespace-level debugfs directory Guixin Liu
2026-06-22 10:44 ` [PATCH 2/2] nvmet: expose reservation state through debugfs Guixin Liu
2026-06-25 7:17 ` [PATCH 0/2] nvmet: add namespace-level debugfs for reservation state Daniel Wagner
2026-06-25 9:10 ` Guixin Liu
2026-07-06 3:10 ` Guixin Liu [this message]
2026-07-06 7:59 ` Daniel Wagner
2026-07-06 10:28 ` Guixin Liu
2026-07-06 12:57 ` Shin'ichiro Kawasaki
2026-07-07 1:42 ` 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=1b56186c-9e5b-4e9a-813e-74e4d1511738@linux.alibaba.com \
--to=kanie@linux.alibaba.com \
--cc=dwagner@suse.de \
--cc=hare@suse.com \
--cc=hch@lst.de \
--cc=kch@nvidia.com \
--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