From: Christoph Hellwig <hch@lst.de>
To: John Garry <john.g.garry@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>,
alx@kernel.org, brauner@kernel.org, djwong@kernel.org,
dchinner@redhat.com, linux-man@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-kernel@vger.kernel.org, ojaswin@linux.ibm.com,
ritesh.list@gmail.com, martin.petersen@oracle.com,
linux-api@vger.kernel.org
Subject: Re: [PATCH RFC] statx.2: Add stx_atomic_write_unit_max_opt
Date: Fri, 4 Apr 2025 11:06:01 +0200 [thread overview]
Message-ID: <20250404090601.GA12163@lst.de> (raw)
In-Reply-To: <5485c1ad-8a20-40bc-aa75-68b820de5e1c@oracle.com>
On Thu, Apr 03, 2025 at 04:07:04PM +0100, John Garry wrote:
> So I am thinking one of these:
> a. stx_atomic_write_unit_max_dev
> b. stx_atomic_write_unit_max_bdev
> c. stx_atomic_write_unit_max_align
> d. stx_atomic_write_unit_max_hw
>
> The terms dev (or device) and bdev are already used in the meaning of some
> members in struct statx, so not too bad. However, when we support large
> atomic writes for XFS rtvol, the bdev atomic write limit and rtextsize
> would influence this value (so just bdev might be a bit misleading in the
> name).
Don't. Especially when you have a natively out of write file system
that optimized case will not involve the usual hardware offload.
next prev parent reply other threads:[~2025-04-04 9:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 11:44 [PATCH RFC] statx.2: Add stx_atomic_write_unit_max_opt John Garry
2025-03-20 7:00 ` Christoph Hellwig
2025-03-20 9:19 ` John Garry
2025-03-20 14:12 ` Christoph Hellwig
2025-03-21 10:20 ` John Garry
2025-03-23 6:40 ` Christoph Hellwig
2025-04-03 15:07 ` John Garry
2025-04-04 9:06 ` Christoph Hellwig [this message]
2025-04-04 9:23 ` John Garry
2025-04-07 6:51 ` 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=20250404090601.GA12163@lst.de \
--to=hch@lst.de \
--cc=alx@kernel.org \
--cc=brauner@kernel.org \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=john.g.garry@oracle.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ojaswin@linux.ibm.com \
--cc=ritesh.list@gmail.com \
/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.