From: Chao Yu <chao@kernel.org>
To: Jan Prusakowski <jprusakowski@google.com>,
Zorro Lang <zlang@kernel.org>,
fstests@vger.kernel.org
Cc: chao@kernel.org, Ojaswin Mujoo <ojaswin@linux.ibm.com>,
Qu Wenruo <wqu@suse.com>, "Darrick J . Wong" <djwong@kernel.org>,
Nirjhar Roy <nirjhar.roy.lists@gmail.com>
Subject: Re: [PATCH] generic/563: allow read tolerance for f2fs in scenario 3
Date: Wed, 20 May 2026 16:14:20 +0800 [thread overview]
Message-ID: <f2e2147e-bf60-4a67-83fe-b77d34f7bc8a@kernel.org> (raw)
In-Reply-To: <20260515082608.449455-1-jprusakowski@google.com>
On 5/15/2026 4:26 PM, Jan Prusakowski wrote:
> F2FS is a log-structured file system that allocates new blocks even for
> overwrites. To perform allocation, it may need to read metadata blocks
> (such as the Node Address Table (NAT) or Segment Info Table (SIT)) if
> they are not already in memory.
>
> In scenario 3 (read -> read/write), unlike scenario 2, there is no prior
> write in the same mount session to load these metadata blocks into memory.
> Therefore, the write operation in the second cgroup triggers metadata
> reads, which are charged to that cgroup.
>
> Relax the read tolerance for f2fs in scenario 3 to accommodate these
> expected metadata reads, matching the tolerance already used in scenario 2.
>
> Signed-off-by: Jan Prusakowski <jprusakowski@google.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
next prev parent reply other threads:[~2026-05-20 8:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 8:26 [PATCH] generic/563: allow read tolerance for f2fs in scenario 3 Jan Prusakowski
2026-05-20 8:14 ` Chao Yu [this message]
2026-05-20 10:25 ` Zorro Lang
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=f2e2147e-bf60-4a67-83fe-b77d34f7bc8a@kernel.org \
--to=chao@kernel.org \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=jprusakowski@google.com \
--cc=nirjhar.roy.lists@gmail.com \
--cc=ojaswin@linux.ibm.com \
--cc=wqu@suse.com \
--cc=zlang@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 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.