mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Wenjie Qi <qwjhust@gmail.com>, jaegeuk@kernel.org
Cc: chao@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, qiwenjie@xiaomi.com
Subject: Re: [RFC PATCH 0/2] f2fs: support uncached buffered I/O
Date: Mon, 17 Aug 2026 17:16:45 +0800	[thread overview]
Message-ID: <fd7c7ecd-1270-48ec-8ecd-89b38545cba5@kernel.org> (raw)
In-Reply-To: <20260806150748.3554436-1-qiwenjie@xiaomi.com>

On 8/6/26 23:07, Wenjie Qi wrote:
> This RFC series enables buffered RWF_DONTCACHE on F2FS.
> 
> The first patch keeps dropbehind folios in dropbehind-only write bios and
> defers their completion to task context when completion happens outside
> in_task().
> 
> The second patch then exposes FOP_DONTCACHE and propagates
> IOCB_DONTCACHE to write_begin folio allocation so buffered
> RWF_DONTCACHE can reach the F2FS write path.
> 
> The split keeps the write-side semantics in place before enabling the
> user-visible API.

Thanks for the patchset.

Do you have some numbers in device? maybe something like Han Qi did in
https://lore.kernel.org/linux-f2fs-devel/20250828121131.3694154-1-hanqi@vivo.com?

Thanks,

> 
> Wenjie Qi (2):
>    f2fs: keep dropbehind write bios task-context safe
>    f2fs: enable buffered RWF_DONTCACHE
> 
>   fs/f2fs/data.c | 63 +++++++++++++++++++++++++++++++++++++++-----------
>   fs/f2fs/file.c |  2 +-
>   2 files changed, 51 insertions(+), 14 deletions(-)
> 


      parent reply	other threads:[~2026-08-17  9:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-06 15:07 Wenjie Qi
2026-08-06 15:07 ` [RFC PATCH 1/2] f2fs: keep dropbehind write bios task-context safe Wenjie Qi
2026-08-06 15:07 ` [RFC PATCH 2/2] f2fs: enable buffered RWF_DONTCACHE Wenjie Qi
2026-08-17  9:16 ` 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=fd7c7ecd-1270-48ec-8ecd-89b38545cba5@kernel.org \
    --to=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=qiwenjie@xiaomi.com \
    --cc=qwjhust@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 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®