From: Christoph Hellwig <hch@infradead.org>
To: Chaitanya Kulkarni <chaitanyak@nvidia.com>
Cc: Christoph Hellwig <hch@infradead.org>,
"alan.adamson@oracle.com" <alan.adamson@oracle.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: Issue with AWUPF when using multiple controllers in a subsystem
Date: Thu, 10 Apr 2025 01:32:33 -0700 [thread overview]
Message-ID: <Z_eCIQ5dtv9oKd9X@infradead.org> (raw)
In-Reply-To: <23d2c5c3-0832-4b62-a151-74a021c63201@nvidia.com>
On Thu, Apr 10, 2025 at 01:33:38AM +0000, Chaitanya Kulkarni wrote:
> if we stop supporting AWUPF and move to NAWUPF then will it break where
> exiting controller's that doesn't support NAWUPF but only supports
> controller wide AWUPF, IOW NSFEAT bit 1 == 0 meaning per-namespace
> atomic info is not valid ? [1]
Yes.
> Looking at the spec NAWUPF values can differ for namespaces attached
> to the same controller and those values can also differ from
> AWUPF ? [2]
That's the whole point of NAWUPF.
> Perhaps using the minimum of all AWUPF and rejecting any ctrl which are
> lower than the initial value is right fix ?
That's what I mean in my previous mail.
next prev parent reply other threads:[~2025-04-10 8:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-04 22:42 Issue with AWUPF when using multiple controllers in a subsystem alan.adamson
2025-04-08 21:08 ` Chaitanya Kulkarni
2025-04-09 9:01 ` Christoph Hellwig
2025-04-10 9:09 ` John Garry
2025-04-10 9:19 ` Christoph Hellwig
2025-04-10 10:11 ` John Garry
2025-04-08 21:08 ` Chaitanya Kulkarni
2025-04-09 9:05 ` Christoph Hellwig
2025-04-10 1:33 ` Chaitanya Kulkarni
2025-04-10 8:32 ` Christoph Hellwig [this message]
2025-04-10 9:07 ` Keith Busch
2025-04-10 9:17 ` Christoph Hellwig
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=Z_eCIQ5dtv9oKd9X@infradead.org \
--to=hch@infradead.org \
--cc=alan.adamson@oracle.com \
--cc=chaitanyak@nvidia.com \
--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