From: Chao Yu <chao@kernel.org>
To: Qi Han <hanqi@vivo.com>, jaegeuk@kernel.org
Cc: chao@kernel.org, axboe@kernel.dk,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] f2fs: f2fs supports uncached buffered I/O
Date: Tue, 15 Jul 2025 14:58:55 +0800 [thread overview]
Message-ID: <d822f21f-bfdb-443a-b639-66860a30ccbd@kernel.org> (raw)
In-Reply-To: <20250715031054.14404-1-hanqi@vivo.com>
On 7/15/25 11:10, Qi Han wrote:
> Jens has already completed the development of uncached buffered I/O
> in git [1], and in f2fs, the feature can be enabled simply by setting
> the FOP_DONTCACHE flag in f2fs_file_operations.
Hi Qi, do you have any numbers of f2fs before/after this change? though
I'm not against supporting this feature in f2fs.
Thanks,
>
> [1]
> https://lore.kernel.org/all/20241220154831.1086649-10-axboe@kernel.dk/T/#m58520a94b46f543d82db3711453dfc7bb594b2b0
>
> Signed-off-by: Qi Han <hanqi@vivo.com>
> ---
> fs/f2fs/file.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
> index 696131e655ed..d8da1fc2febf 100644
> --- a/fs/f2fs/file.c
> +++ b/fs/f2fs/file.c
> @@ -5425,5 +5425,5 @@ const struct file_operations f2fs_file_operations = {
> .splice_read = f2fs_file_splice_read,
> .splice_write = iter_file_splice_write,
> .fadvise = f2fs_file_fadvise,
> - .fop_flags = FOP_BUFFER_RASYNC,
> + .fop_flags = FOP_BUFFER_RASYNC | FOP_DONTCACHE,
> };
next prev parent reply other threads:[~2025-07-15 6:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 3:10 [PATCH] f2fs: f2fs supports uncached buffered I/O Qi Han
2025-07-15 6:58 ` Chao Yu [this message]
2025-07-15 8:14 ` hanqi
2025-07-15 14:28 ` Jens Axboe
2025-07-16 3:34 ` hanqi
2025-07-16 3:43 ` Jens Axboe
2025-07-16 8:27 ` hanqi
2025-07-24 13:09 ` Chao Yu
2025-07-25 1:44 ` hanqi
2025-07-25 2:37 ` Chao Yu
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=d822f21f-bfdb-443a-b639-66860a30ccbd@kernel.org \
--to=chao@kernel.org \
--cc=axboe@kernel.dk \
--cc=hanqi@vivo.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).