From: Eric Biggers <ebiggers@kernel.org> To: linux-fsdevel@vger.kernel.org Cc: linux-ext4@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, linux-xfs@vger.kernel.org, linux-api@vger.kernel.org, linux-fscrypt@vger.kernel.org, linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, Keith Busch <kbusch@kernel.org> Subject: [PATCH v3 8/8] f2fs: support STATX_DIOALIGN Date: Thu, 16 Jun 2022 13:15:06 -0700 [thread overview] Message-ID: <20220616201506.124209-9-ebiggers@kernel.org> (raw) In-Reply-To: <20220616201506.124209-1-ebiggers@kernel.org> From: Eric Biggers <ebiggers@google.com> Add support for STATX_DIOALIGN to f2fs, so that direct I/O alignment restrictions are exposed to userspace in a generic way. Signed-off-by: Eric Biggers <ebiggers@google.com> --- fs/f2fs/file.c | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c index 1b452bb75af29..11d75aa3da185 100644 --- a/fs/f2fs/file.c +++ b/fs/f2fs/file.c @@ -852,6 +852,21 @@ int f2fs_getattr(struct user_namespace *mnt_userns, const struct path *path, stat->btime.tv_nsec = fi->i_crtime.tv_nsec; } + /* + * Return the DIO alignment restrictions if requested. We only return + * this information when requested, since on encrypted files it might + * take a fair bit of work to get if the file wasn't opened recently. + */ + if ((request_mask & STATX_DIOALIGN) && S_ISREG(inode->i_mode)) { + unsigned int bsize = i_blocksize(inode); + + stat->result_mask |= STATX_DIOALIGN; + if (!f2fs_force_buffered_io(inode)) { + stat->dio_mem_align = bsize; + stat->dio_offset_align = bsize; + } + } + flags = fi->i_flags; if (flags & F2FS_COMPR_FL) stat->attributes |= STATX_ATTR_COMPRESSED; -- 2.36.1
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers@kernel.org> To: linux-fsdevel@vger.kernel.org Cc: linux-block@vger.kernel.org, linux-api@vger.kernel.org, linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, linux-xfs@vger.kernel.org, linux-fscrypt@vger.kernel.org, Keith Busch <kbusch@kernel.org>, linux-ext4@vger.kernel.org Subject: [f2fs-dev] [PATCH v3 8/8] f2fs: support STATX_DIOALIGN Date: Thu, 16 Jun 2022 13:15:06 -0700 [thread overview] Message-ID: <20220616201506.124209-9-ebiggers@kernel.org> (raw) In-Reply-To: <20220616201506.124209-1-ebiggers@kernel.org> From: Eric Biggers <ebiggers@google.com> Add support for STATX_DIOALIGN to f2fs, so that direct I/O alignment restrictions are exposed to userspace in a generic way. Signed-off-by: Eric Biggers <ebiggers@google.com> --- fs/f2fs/file.c | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c index 1b452bb75af29..11d75aa3da185 100644 --- a/fs/f2fs/file.c +++ b/fs/f2fs/file.c @@ -852,6 +852,21 @@ int f2fs_getattr(struct user_namespace *mnt_userns, const struct path *path, stat->btime.tv_nsec = fi->i_crtime.tv_nsec; } + /* + * Return the DIO alignment restrictions if requested. We only return + * this information when requested, since on encrypted files it might + * take a fair bit of work to get if the file wasn't opened recently. + */ + if ((request_mask & STATX_DIOALIGN) && S_ISREG(inode->i_mode)) { + unsigned int bsize = i_blocksize(inode); + + stat->result_mask |= STATX_DIOALIGN; + if (!f2fs_force_buffered_io(inode)) { + stat->dio_mem_align = bsize; + stat->dio_offset_align = bsize; + } + } + flags = fi->i_flags; if (flags & F2FS_COMPR_FL) stat->attributes |= STATX_ATTR_COMPRESSED; -- 2.36.1 _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2022-06-16 20:18 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-16 20:14 [PATCH v3 0/8] make statx() return DIO alignment information Eric Biggers 2022-06-16 20:14 ` [f2fs-dev] " Eric Biggers 2022-06-16 20:14 ` [PATCH v3 1/8] statx: add direct I/O " Eric Biggers 2022-06-16 20:14 ` [f2fs-dev] " Eric Biggers 2022-06-19 11:30 ` Avi Kivity 2022-06-19 11:30 ` [f2fs-dev] " Avi Kivity 2022-06-26 7:44 ` Christoph Hellwig 2022-06-26 7:44 ` [f2fs-dev] " Christoph Hellwig 2022-06-26 10:20 ` Avi Kivity 2022-06-26 10:20 ` [f2fs-dev] " Avi Kivity via Linux-f2fs-devel 2022-06-23 15:58 ` Darrick J. Wong 2022-06-23 15:58 ` [f2fs-dev] " Darrick J. Wong 2022-06-23 17:23 ` Eric Biggers 2022-06-23 17:23 ` Eric Biggers 2022-06-23 18:58 ` [f2fs-dev] " Eric Biggers 2022-06-23 18:58 ` Eric Biggers 2022-06-26 8:02 ` Christoph Hellwig 2022-06-26 8:02 ` [f2fs-dev] " Christoph Hellwig 2022-06-26 7:44 ` Christoph Hellwig 2022-06-26 7:44 ` [f2fs-dev] " Christoph Hellwig 2022-06-16 20:15 ` [PATCH v3 2/8] vfs: support STATX_DIOALIGN on block devices Eric Biggers 2022-06-16 20:15 ` [f2fs-dev] " Eric Biggers 2022-06-26 7:48 ` Christoph Hellwig 2022-06-26 7:48 ` [f2fs-dev] " Christoph Hellwig 2022-06-16 20:15 ` [PATCH v3 3/8] fscrypt: change fscrypt_dio_supported() to prepare for STATX_DIOALIGN Eric Biggers 2022-06-16 20:15 ` [f2fs-dev] " Eric Biggers 2022-06-16 20:15 ` [PATCH v3 4/8] ext4: support STATX_DIOALIGN Eric Biggers 2022-06-16 20:15 ` [f2fs-dev] " Eric Biggers 2022-06-16 20:15 ` [PATCH v3 5/8] f2fs: move f2fs_force_buffered_io() into file.c Eric Biggers 2022-06-16 20:15 ` [f2fs-dev] " Eric Biggers 2022-06-16 20:15 ` [PATCH v3 6/8] f2fs: don't allow DIO reads but not DIO writes Eric Biggers 2022-06-16 20:15 ` [f2fs-dev] " Eric Biggers 2022-06-16 20:15 ` [PATCH v3 7/8] f2fs: simplify f2fs_force_buffered_io() Eric Biggers 2022-06-16 20:15 ` [f2fs-dev] " Eric Biggers 2022-06-16 20:15 ` Eric Biggers [this message] 2022-06-16 20:15 ` [f2fs-dev] [PATCH v3 8/8] f2fs: support STATX_DIOALIGN Eric Biggers 2022-07-20 5:03 ` [PATCH v3 0/8] make statx() return DIO alignment information Christoph Hellwig 2022-07-20 5:03 ` [f2fs-dev] " 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=20220616201506.124209-9-ebiggers@kernel.org \ --to=ebiggers@kernel.org \ --cc=kbusch@kernel.org \ --cc=linux-api@vger.kernel.org \ --cc=linux-block@vger.kernel.org \ --cc=linux-ext4@vger.kernel.org \ --cc=linux-f2fs-devel@lists.sourceforge.net \ --cc=linux-fscrypt@vger.kernel.org \ --cc=linux-fsdevel@vger.kernel.org \ --cc=linux-kernel@vger.kernel.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: linkBe 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.