From: Christoph Hellwig <hch@lst.de>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: John Garry <john.g.garry@oracle.com>,
Christoph Hellwig <hch@lst.de>,
Christoph Hellwig <hch@infradead.org>,
linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-block@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: Re: Do we need an opt-in for file systems use of hw atomic writes?
Date: Tue, 19 Aug 2025 16:45:45 +0200 [thread overview]
Message-ID: <20250819144545.GA18364@lst.de> (raw)
In-Reply-To: <20250819144347.GC7942@frogsfrogsfrogs>
On Tue, Aug 19, 2025 at 07:43:47AM -0700, Darrick J. Wong wrote:
> What is the likelihood of convincing the nvme standards folks to add a
> new command for write-untorn that doesn't just silently fail if you get
> the parameters wrong?
In my experience that depends mostly on how much a big customers for
NVMe hardware is asking for it. Hint: while Oracle isn't in the
absolute top tier of the influence scale it probably is just below.
next prev parent reply other threads:[~2025-08-19 14:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 13:17 Do we need an opt-in for file systems use of hw atomic writes? Christoph Hellwig
2025-07-14 13:24 ` Theodore Ts'o
2025-07-14 13:30 ` Christoph Hellwig
2025-07-14 16:04 ` Darrick J. Wong
2025-07-15 6:00 ` Christoph Hellwig
2025-07-15 3:22 ` Martin K. Petersen
2025-07-15 6:00 ` Christoph Hellwig
2025-07-15 12:45 ` Martin K. Petersen
2025-07-14 13:39 ` John Garry
2025-07-14 13:50 ` Christoph Hellwig
2025-07-14 15:53 ` John Garry
2025-07-15 6:02 ` Christoph Hellwig
2025-07-15 8:42 ` John Garry
2025-07-15 9:03 ` Christoph Hellwig
2025-08-19 11:42 ` John Garry
2025-08-19 13:39 ` Christoph Hellwig
2025-08-19 14:36 ` John Garry
2025-08-19 14:43 ` Darrick J. Wong
2025-08-19 14:45 ` Christoph Hellwig [this message]
2025-08-21 14:01 ` Keith Busch
2025-07-15 10:02 ` Christian Brauner
2025-07-15 11:29 ` Christoph Hellwig
2025-07-15 12:20 ` Christian Brauner
2025-07-15 11:58 ` Theodore Ts'o
2025-07-14 20:53 ` Dave Chinner
2025-07-15 6:05 ` Christoph Hellwig
2025-07-15 20:56 ` Keith Busch
2025-07-16 5:50 ` Nilay Shroff
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=20250819144545.GA18364@lst.de \
--to=hch@lst.de \
--cc=djwong@kernel.org \
--cc=hch@infradead.org \
--cc=john.g.garry@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-xfs@vger.kernel.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 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.