All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@kernel.org>
To: Nilay Shroff <nilay@linux.ibm.com>
Cc: John Garry <john.g.garry@oracle.com>,
	axboe@kernel.dk, hch@lst.de, sagi@grimberg.me,
	linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
	tytso@mit.edu, martin.petersen@oracle.com, djwong@kernel.org,
	mcgrof@infradead.org
Subject: Re: [RFC PATCH] nvme: add an opt-in to use AWUPF
Date: Thu, 21 Aug 2025 07:42:36 -0600	[thread overview]
Message-ID: <aKciTPKiL8wRWmHA@kbusch-mbp> (raw)
In-Reply-To: <b8156bb1-b7fe-4036-9dbb-98fdcec3ff65@linux.ibm.com>

On Thu, Aug 21, 2025 at 10:55:31AM +0530, Nilay Shroff wrote:
> On 8/21/25 3:21 AM, Keith Busch wrote:
> > I tried to list out conditions for when I think the value could be counted on here:
> > 
> >   https://lore.kernel.org/linux-nvme/aGvuRS8VmC0JXAR3@kbusch-mbp/
> > 
> Regarding the checks you listed, they seem too restrictive. They only support
> AWUPF for single-controller devices and for disks that either have only one
> namespace or support formatting all namespaces together (i.e., do not support
> formatting individual namespaces).

Being restrictive was the point. It constrains to 1.0 type behavior
where things were much simpler. I am just shocked vendors went through
the trouble to implement the complicated features but couldn't be
bothered to do the trivial one that makes it useful.


  reply	other threads:[~2025-08-21 19:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-20 15:02 [RFC PATCH] nvme: add an opt-in to use AWUPF John Garry
2025-08-20 21:51 ` Keith Busch
2025-08-21  5:25   ` Nilay Shroff
2025-08-21 13:42     ` Keith Busch [this message]
2025-08-21  8:38   ` Christoph Hellwig
2025-08-21 10:56   ` John Garry
2025-08-21  8:35 ` Christoph Hellwig
2025-08-21 10:33   ` John Garry

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=aKciTPKiL8wRWmHA@kbusch-mbp \
    --to=kbusch@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=djwong@kernel.org \
    --cc=hch@lst.de \
    --cc=john.g.garry@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=martin.petersen@oracle.com \
    --cc=mcgrof@infradead.org \
    --cc=nilay@linux.ibm.com \
    --cc=sagi@grimberg.me \
    --cc=tytso@mit.edu \
    /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.