From: Christian Brauner <brauner@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Chandan Babu R <chandan.babu@oracle.com>,
"Darrick J. Wong" <djwong@kernel.org>,
Hongbo Li <lihongbo22@huawei.com>,
Ryusuke Konishi <konishi.ryusuke@gmail.com>,
linux-nilfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-xfs@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>
Subject: Re: add STATX_DIO_READ_ALIGN v3
Date: Thu, 9 Jan 2025 16:24:28 +0100 [thread overview]
Message-ID: <20250109-neigen-eisern-3024e1ffbde0@brauner> (raw)
In-Reply-To: <20250109083109.1441561-1-hch@lst.de>
On Thu, 9 Jan 2025 09:31:00 +0100, Christoph Hellwig wrote:
> [I hope that no one gets too annoyed by the rapid resends, but s we're
> down to comment an man page tweaks I thought I'd stick to the fast pace]
>
> file systems that write out of place usually require different alignment
> for direct I/O writes than what they can do for reads. This series tries
> to address this by adding yet another statx field.
>
> [...]
Applied to the vfs-6.14.statx.dio branch of the vfs/vfs.git tree.
Patches in the vfs-6.14.statx.dio branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs-6.14.statx.dio
[1/5] fs: reformat the statx definition
https://git.kernel.org/vfs/vfs/c/8fc7e23a9bd8
[2/5] fs: add STATX_DIO_READ_ALIGN
https://git.kernel.org/vfs/vfs/c/7ed6cbe0f8ca
[3/5] xfs: cleanup xfs_vn_getattr
https://git.kernel.org/vfs/vfs/c/7e17483c7b15
[4/5] xfs: report the correct read/write dio alignment for reflinked inodes
https://git.kernel.org/vfs/vfs/c/7422bbd03021
[5/5] xfs: report larger dio alignment for COW inodes
https://git.kernel.org/vfs/vfs/c/468210ec76e1
prev parent reply other threads:[~2025-01-09 15:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 8:31 add STATX_DIO_READ_ALIGN v3 Christoph Hellwig
2025-01-09 8:31 ` [PATCH 1/5] fs: reformat the statx definition Christoph Hellwig
2025-01-09 8:31 ` [PATCH 2/5] fs: add STATX_DIO_READ_ALIGN Christoph Hellwig
2025-01-09 8:31 ` [PATCH 3/5] xfs: cleanup xfs_vn_getattr Christoph Hellwig
2025-01-09 8:31 ` [PATCH 4/5] xfs: report the correct read/write dio alignment for reflinked inodes Christoph Hellwig
2025-01-09 8:31 ` [PATCH 5/5] xfs: report larger dio alignment for COW inodes Christoph Hellwig
2025-01-09 8:32 ` [PATCH] statx.2: document STATX_DIO_READ_ALIGN Christoph Hellwig
2025-01-09 13:21 ` Alejandro Colomar
2025-01-09 15:24 ` Christian Brauner [this message]
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=20250109-neigen-eisern-3024e1ffbde0@brauner \
--to=brauner@kernel.org \
--cc=chandan.babu@oracle.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=konishi.ryusuke@gmail.com \
--cc=lihongbo22@huawei.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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