From: Chao Yu <chao@kernel.org>
To: "yohan.joung" <yohan.joung@sk.com>, jaegeuk@kernel.org
Cc: chao@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, pilhyun.kim@sk.com
Subject: Re: [PATCH v2] f2fs: zone: wait for inflight dio completion, excluding pinned files read using dio
Date: Tue, 22 Jul 2025 13:51:53 +0800 [thread overview]
Message-ID: <33e75ec8-9bf4-4c45-b706-a2e6b6cd8413@kernel.org> (raw)
In-Reply-To: <20250722052046.1445-1-yohan.joung@sk.com>
On 7/22/25 13:20, yohan.joung wrote:
> read for the pinfile using Direct I/O do not wait for dio write.
>
> Signed-off-by: yohan.joung <yohan.joung@sk.com>
> ---
> fs/f2fs/file.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
> index 4039ccb5022c..2b7e5c46c1ae 100644
> --- a/fs/f2fs/file.c
> +++ b/fs/f2fs/file.c
> @@ -4834,6 +4834,7 @@ static ssize_t f2fs_file_read_iter(struct kiocb *iocb, struct iov_iter *to)
> struct inode *inode = file_inode(iocb->ki_filp);
> const loff_t pos = iocb->ki_pos;
> ssize_t ret;
> + bool dio;
>
> if (!f2fs_is_compress_backend_ready(inode))
> return -EOPNOTSUPP;
> @@ -4842,12 +4843,15 @@ static ssize_t f2fs_file_read_iter(struct kiocb *iocb, struct iov_iter *to)
> f2fs_trace_rw_file_path(iocb->ki_filp, iocb->ki_pos,
> iov_iter_count(to), READ);
>
> + dio = f2fs_should_use_dio(inode, iocb, to);
> +
> /* In LFS mode, if there is inflight dio, wait for its completion */
> if (f2fs_lfs_mode(F2FS_I_SB(inode)) &&
> - get_pages(F2FS_I_SB(inode), F2FS_DIO_WRITE))
> + get_pages(F2FS_I_SB(inode), F2FS_DIO_WRITE) &&
> + !(f2fs_is_pinned_file(inode) && dio))
How about?
(!f2fs_is_pinned_file(inode) || !dio)
Thanks,
> inode_dio_wait(inode);
>
> - if (f2fs_should_use_dio(inode, iocb, to)) {
> + if (dio) {
> ret = f2fs_dio_read_iter(iocb, to);
> } else {
> ret = filemap_read(iocb, to, 0);
prev parent reply other threads:[~2025-07-22 5:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 5:20 yohan.joung
2025-07-22 5:51 ` Chao Yu [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=33e75ec8-9bf4-4c45-b706-a2e6b6cd8413@kernel.org \
--to=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pilhyun.kim@sk.com \
--cc=yohan.joung@sk.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 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®