mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Chao Shi <coshi036@gmail.com>,
	linux-nvme@lists.infradead.org, Sagi Grimberg <sagi@grimberg.me>,
	Jens Axboe <axboe@kernel.dk>,
	Tatsuya Sasaki <tatsuya6.sasaki@kioxia.com>,
	Maurizio Lombardi <mlombard@arkamax.eu>,
	linux-kernel@vger.kernel.org, Sungwoo Kim <iam@sung-woo.kim>,
	Dave Tian <daveti@purdue.edu>, Weidong Zhu <weizhu@fiu.edu>
Subject: Re: [PATCH v2] nvme: reserve a keep-alive admin tag for all transports
Date: Thu, 21 May 2026 08:38:29 -0600	[thread overview]
Message-ID: <ag8Y5c3sjYFZzan5@kbusch-mbp> (raw)
In-Reply-To: <20260521082549.GA11208@lst.de>

On Thu, May 21, 2026 at 10:25:49AM +0200, Christoph Hellwig wrote:
> On Wed, May 20, 2026 at 02:26:13PM -0600, Keith Busch wrote:
> > I am skeptical anyone would produce a PCIe device that supports it, but
> > let's say someone does: what is the use case motivating enabling this
> > optional feature in this driver? If it's just because the option is
> > there, then I think we can just reject the user command submitting the
> > feature for PCIe transports, like I earlier suggested. Requiring an
> > active command will just harm idle power states.
> 
> I don't think that's quite the point.  We'd have to add special
> filtering to fix the reproducer.  Compared to that just reserving
> a tag and officially supporting the feature is much easier and a much
> better story.

This command is already special since we filter for it on the completion
side. We may want to selectively filter other Set Feature commands too.
For example, we don't want user space turning on Host Dispersed
Namespace Support, because this driver is not going to correctly react
to that one either.

  reply	other threads:[~2026-05-21 14:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-15  7:12 Chao Shi
2026-05-19  7:14 ` Christoph Hellwig
2026-05-20 20:26 ` Keith Busch
2026-05-21  8:25   ` Christoph Hellwig
2026-05-21 14:38     ` Keith Busch [this message]
2026-05-22 12:14       ` Christoph Hellwig
2026-05-22 15:32         ` Chao S
2026-05-22 15:33       ` Chao S

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=ag8Y5c3sjYFZzan5@kbusch-mbp \
    --to=kbusch@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=coshi036@gmail.com \
    --cc=daveti@purdue.edu \
    --cc=hch@lst.de \
    --cc=iam@sung-woo.kim \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=mlombard@arkamax.eu \
    --cc=sagi@grimberg.me \
    --cc=tatsuya6.sasaki@kioxia.com \
    --cc=weizhu@fiu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome