mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <kbusch@kernel.org>
Cc: Erwan Velu <e.velu@criteo.com>,
	linux-nvme@lists.infradead.org, axboe@kernel.dk, hch@lst.de,
	sagi@grimberg.me, linux-kernel@vger.kernel.org,
	Erwan Velu <erwanaliasr1@gmail.com>
Subject: Re: [PATCH] nvme: honor the volatile write cache enable state
Date: Wed, 28 Oct 2026 17:16:39 +0100	[thread overview]
Message-ID: <20261028161639.GA21871@lst.de> (raw)
In-Reply-To: <auId5RuBhMFGirJ1@kbusch-mbp>

On Wed, Oct 28, 2026 at 10:08:05AM -0600, Keith Busch wrote:
> > Considering the performance impact for these type of device,s would you be
> > open to a backport to stable once merged ?
> 
> Not sure when a performance improvement is stable worthy. I'm more
> concerned that doing this is going to expose corruption, but it's what
> the device is asking for, so fine to introduce it, but stable is
> questionable.

Same here.  We should not send these improvements to stable, but let
them soak in linux-next and mainline.


  reply	other threads:[~2026-10-28 16:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-16 14:12 Erwan Velu
2026-10-16 16:57 ` Keith Busch
2026-10-16 17:15   ` Erwan Velu
2026-10-16 17:27     ` Keith Busch
2026-10-16 17:43       ` Erwan Velu
2026-10-16 17:55         ` Keith Busch
2026-10-17  4:25           ` Erwan Velu
2026-10-22 13:27             ` Erwan Velu
2026-10-22 23:17               ` Keith Busch
2026-10-23 14:53                 ` Erwan Velu
2026-10-28 16:08                   ` Keith Busch
2026-10-28 16:16                     ` Christoph Hellwig [this message]
2026-10-28 17:08                     ` Erwan Velu
2026-10-28 17:47                       ` Keith Busch

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=20261028161639.GA21871@lst.de \
    --to=hch@lst.de \
    --cc=axboe@kernel.dk \
    --cc=e.velu@criteo.com \
    --cc=erwanaliasr1@gmail.com \
    --cc=kbusch@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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

all inboxes | Powered by JetHome®