From: Sagi Grimberg <sagi@grimberg.me>
To: Wen Xiong <wenxiong@linux.ibm.com>, Keith Busch <kbusch@kernel.org>
Cc: linux-nvme@lists.infradead.org, Gjoyce <gjoyce@ibm.com>,
Nilay Shroff <nilay@linux.ibm.com>,
Wenxiong <wenxiong@us.ibm.com>
Subject: Re: [PATCH V2] nvme: Add module reference counting for multipath devices
Date: Mon, 31 Aug 2026 00:46:13 +0300 [thread overview]
Message-ID: <558c74c2-4e96-4ef5-b0e3-7a23a08df4d5@grimberg.me> (raw)
In-Reply-To: <5626e2342490081fc4acb47f370009ba@linux.ibm.com>
On 25/08/2026 22:11, Wen Xiong wrote:
> On 2026-08-22 19:46, Sagi Grimberg wrote:
>
>> OK, I now read the original report regarding nvme root device. please
>> disregard.
>
> Hi Keith and Sagi,
>
> For single port nvme device, I found out:
> If NS does not have any filesystems configured and the root filesystem
> is located on another SCSI disk, the NVMe device's reference count is 0.
> When a filesystem is created on NS, the NVMe device's reference count
> increases to 1.
>
> With my V2 patch for multipath devices,
> Nvme's reference count always increases if NS doesn't have any
> filesystem configured.
> If nvme1 has 1 NS without any filesystem, reference count is 2 after
> system boots up.
>
> Should Nvme's reference count increases if no filesystem configured on
> a NS?
No I dont think it should
next prev parent reply other threads:[~2026-08-30 21:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 22:32 [PATCH V2] nvme: Add module reference counting for multipath devices wenxiong
2026-08-20 4:19 ` Nares Bannoth
2026-08-23 0:20 ` Sagi Grimberg
2026-08-23 0:46 ` Sagi Grimberg
2026-08-24 20:23 ` Wen Xiong
2026-08-25 19:11 ` Wen Xiong
2026-08-30 21:46 ` Sagi Grimberg [this message]
2026-08-26 12:40 ` Nilay Shroff
2026-08-26 14:23 ` Keith Busch
2026-08-26 16:18 ` Wen Xiong
2026-08-26 16:36 ` Keith Busch
2026-08-27 13:21 ` Nilay Shroff
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=558c74c2-4e96-4ef5-b0e3-7a23a08df4d5@grimberg.me \
--to=sagi@grimberg.me \
--cc=gjoyce@ibm.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=nilay@linux.ibm.com \
--cc=wenxiong@linux.ibm.com \
--cc=wenxiong@us.ibm.com \
/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