From: Christoph Hellwig <hch@lst.de>
To: alan.adamson@oracle.com
Cc: Christoph Hellwig <hch@lst.de>, Keith Busch <kbusch@kernel.org>,
Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org, Yi Zhang <yi.zhang@redhat.com>,
John Garry <john.g.garry@oracle.com>
Subject: Re: fix atomic limits check v2
Date: Thu, 26 Jun 2025 07:22:19 +0200 [thread overview]
Message-ID: <20250626052219.GA23726@lst.de> (raw)
In-Reply-To: <69e9b54f-c3c7-45c3-b4aa-4dbb9df64976@oracle.com>
On Wed, Jun 25, 2025 at 10:04:55AM -0700, alan.adamson@oracle.com wrote:
> [root@localhost ~]# nvme id-ns /dev/nvme0n2 | grep nawupf
> nawupf : 15
> [root@localhost ~]# cat /sys/block/nvme0n2/queue/atomic_write_max_bytes
> 8192
> [root@localhost ~]# nvme id-ns /dev/nvme0n3 | grep nawupf
> nawupf : 63
> [root@localhost ~]# cat /sys/block/nvme0n3/queue/atomic_write_max_bytes
> 32768
> [root@localhost ~]# dmesg | grep nvme | grep AWUPF
> [ 2.761599] nvme nvme2: inconsistent AWUPF, controller not added (7/15).
> [ 2.765669] nvme nvme1: inconsistent AWUPF, controller not added (31/15).
> [root@localhost ~]#
>
> Why was CTRL1 (nvme1) not added? AWUPF of 31 works with a
> atomic_write_max_bytes of 8192.
Because it reports different AWUPF for controllers in the same subsystem.
prev parent reply other threads:[~2025-06-26 5:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 6:39 fix atomic limits check v2 Christoph Hellwig
2025-06-25 6:39 ` [PATCH 1/2] nvme: refactor the atomic write unit detection Christoph Hellwig
2025-06-25 6:39 ` [PATCH 2/2] nvme: fix atomic write size validation Christoph Hellwig
2025-06-27 0:05 ` Uday Shankar
2025-06-27 0:18 ` Yi Zhang
2025-06-25 17:04 ` fix atomic limits check v2 alan.adamson
2025-06-26 5:22 ` Christoph Hellwig [this message]
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=20250626052219.GA23726@lst.de \
--to=hch@lst.de \
--cc=alan.adamson@oracle.com \
--cc=john.g.garry@oracle.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=yi.zhang@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.