From: Chao Yu <chao@kernel.org>
To: jaegeuk@kernel.org
Cc: chao@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] f2fs: introduce max_atc_write_bio_entry_cnt
Date: Sat, 17 Oct 2026 10:16:14 +0800 [thread overview]
Message-ID: <abeed257-b8d2-4c1d-9ee9-5e93f628348e@kernel.org> (raw)
In-Reply-To: <20261007114949.2428048-5-chao@kernel.org>
As discussed offline, we can drop this sysfs version patch, and use below two
patches instead:
[PATCH 1/2] f2fs: introduce max_write_bio_{folio,entry}_cnt module parameters
[PATCH 2/2] f2fs: remove max_atc_write_bio_size
Jaegeuk, fyi, these two patches can be applied right after "f2fs: cache: support
asynchronous write_end_io".
Thanks,
On 10/7/26 19:49, Chao Yu wrote:
> From: Chao Yu <chao@kernel.org>
>
> Commit 3de6b8094115 ("f2fs: Run f2fs_write_end_io() asynchronously")
> introduced max_atc_write_bio_size to offload write bio completion to a
> workqueue when f2fs_write_end_io() is called in atomic context.
>
> However, using the bio byte size (bi_iter.bi_size) as the threshold has
> limitations once large folios or multi-page bvecs are involved:
>
> 1. In f2fs_write_end_bio(), execution time is dominated by the
> completion loop (bio_for_each_folio_all() for pagecache folios,
> or while(entry) for cached metadata blocks), where per-entry
> locking, status clearing, sanity checks, and writeback end are
> performed. The CPU latency in atomic context scales with the number
> of entries in the bio, not its byte size.
> 2. For large folios, a large bio (e.g. 1MB comprised of single large
> folios) only iterates a few times through the loop. Throttling solely
> by max_atc_write_bio_size unnecessarily offloads such low-latency
> bios to the workqueue, adding context-switch overhead.
> 3. Conversely, relying on bio->bi_vcnt is insufficient because the block
> layer (bvec_try_merge_page) merges physically consecutive pages/folios
> into the same bio_vec segment. Thus, a bio with bi_vcnt == 1 could
> still contain multiple entries and iterate many times in end_io.
>
> To address this, track the exact number of entries (folios or cached
> blocks) queued to the write bio via entry_cnt in struct f2fs_bio, and
> introduce a sysfs attribute max_atc_write_bio_entry_cnt. This enables
> precise control over atomic context latency without penalizing large
> folios.
>
> Signed-off-by: Chao Yu <chao@kernel.org>
> ---
> Documentation/ABI/testing/sysfs-fs-f2fs | 11 +++++++++++
> fs/f2fs/data.c | 7 ++++++-
> fs/f2fs/f2fs.h | 3 +++
> fs/f2fs/super.c | 1 +
> fs/f2fs/sysfs.c | 2 ++
> 5 files changed, 23 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/ABI/testing/sysfs-fs-f2fs b/Documentation/ABI/testing/sysfs-fs-f2fs
> index f50739f90ae9..5ff693dd4bff 100644
> --- a/Documentation/ABI/testing/sysfs-fs-f2fs
> +++ b/Documentation/ABI/testing/sysfs-fs-f2fs
> @@ -1014,6 +1014,17 @@ Description: Every time a write operation completes f2fs_write_end_io() is
> (atc) context. The default value for this attribute is UINT_MAX
> which means that this functionality is disabled by default.
>
> +What: /sys/fs/f2fs/<disk>/max_atc_write_bio_entry_cnt
> +Date: October 2026
> +Contact: Chao Yu <chao@kernel.org>
> +Description: Every time a write operation completes f2fs_write_end_io() is
> + called. This function may be called from an atomic context,
> + e.g. from inside an interrupt handler. This attribute controls
> + the maximum number of entries (folios or cached blocks) in a
> + write bio that is completed in atomic (atc) context. The default
> + value for this attribute is UINT_MAX which means that this
> + functionality is disabled by default.
> +
> What: /sys/fs/f2fs/<disk>/pinned_area_max_secno
> Date: August 2026
> Contact: "Daeho Jeong" <daehojeong@google.com>
> diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
> index 0a6aa24caa07..395794d00194 100644
> --- a/fs/f2fs/data.c
> +++ b/fs/f2fs/data.c
> @@ -398,7 +398,8 @@ static void f2fs_write_end_io(struct bio *bio)
>
> sbi = bio->bi_private;
>
> - if (in_atomic() && bio->bi_iter.bi_size > sbi->max_atc_write_bio_size) {
> + if (in_atomic() && (bio->bi_iter.bi_size > sbi->max_atc_write_bio_size ||
> + F2FS_BIO(bio)->entry_cnt > sbi->max_atc_write_bio_entry_cnt)) {
> struct work_struct *w;
>
> w = &container_of(bio, struct f2fs_bio, bio)->work;
> @@ -551,6 +552,7 @@ static struct bio *__bio_alloc(struct f2fs_io_info *fio, int npages)
> fio->type, fio->temp);
> bio->bi_write_stream = f2fs_io_type_to_write_stream(bdev, fio->type,
> fio->temp);
> + F2FS_BIO(bio)->entry_cnt = 0;
> }
> iostat_alloc_and_bind_ctx(sbi, bio, NULL);
>
> @@ -1218,6 +1220,8 @@ void f2fs_submit_page_write(struct f2fs_io_info *fio)
> goto alloc_new;
> }
>
> + F2FS_BIO(io->bio)->entry_cnt++;
> +
> if (fio->io_wbc)
> wbc_account_cgroup_owner(fio->io_wbc, fio->folio,
> folio_size(fio->folio));
> @@ -1324,6 +1328,7 @@ void f2fs_submit_cache_write(struct f2fs_io_info *fio)
> }
>
> f2fs_bio_add_cache(fio, io->bio);
> + F2FS_BIO(io->bio)->entry_cnt++;
>
> io->last_block_in_bio = fio->new_blkaddr;
>
> diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h
> index 089a62c054ea..0acbc4d299af 100644
> --- a/fs/f2fs/f2fs.h
> +++ b/fs/f2fs/f2fs.h
> @@ -1778,6 +1778,7 @@ struct f2fs_gc_kthread {
> struct f2fs_bio {
> struct work_struct work;
> struct f2fs_cached_block *entry;
> + unsigned int entry_cnt;
> struct bio bio;
> };
>
> @@ -1807,6 +1808,8 @@ struct f2fs_sb_info {
> /* for bio operations */
> /* Largest write bio size completed in atomic context (atc). */
> u32 max_atc_write_bio_size;
> + /* Largest write bio entry count completed in atomic context (atc). */
> + u32 max_atc_write_bio_entry_cnt;
> struct f2fs_bio_info *write_io[NR_PAGE_TYPE]; /* for write bios */
> /* keep migration IO order for LFS mode */
> struct f2fs_rwsem io_order_lock;
> diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
> index d683240040f0..9e55febe18f4 100644
> --- a/fs/f2fs/super.c
> +++ b/fs/f2fs/super.c
> @@ -5211,6 +5211,7 @@ static int f2fs_fill_super(struct super_block *sb, struct fs_context *fc)
> goto free_sb_buf;
> }
> sbi->max_atc_write_bio_size = UINT_MAX;
> + sbi->max_atc_write_bio_entry_cnt = UINT_MAX;
>
> INIT_WORK(&sbi->s_error_work, f2fs_record_error_work);
> memcpy(sbi->errors, raw_super->s_errors, MAX_F2FS_ERRORS);
> diff --git a/fs/f2fs/sysfs.c b/fs/f2fs/sysfs.c
> index 95f8dc0c4218..32dfd564094b 100644
> --- a/fs/f2fs/sysfs.c
> +++ b/fs/f2fs/sysfs.c
> @@ -1285,6 +1285,7 @@ F2FS_SBI_RW_ATTR(umount_discard_timeout, interval_time[UMOUNT_DISCARD_TIMEOUT]);
> F2FS_SBI_RW_ATTR(gc_pin_file_thresh, gc_pin_file_threshold);
> F2FS_SBI_RW_ATTR(gc_reclaimed_segments, gc_reclaimed_segs);
> F2FS_SBI_RW_ATTR(max_atc_write_bio_size, max_atc_write_bio_size);
> +F2FS_SBI_RW_ATTR(max_atc_write_bio_entry_cnt, max_atc_write_bio_entry_cnt);
> F2FS_SBI_GENERAL_RW_ATTR(max_victim_search);
> F2FS_SBI_GENERAL_RW_ATTR(migration_granularity);
> F2FS_SBI_GENERAL_RW_ATTR(migration_window_granularity);
> @@ -1536,6 +1537,7 @@ static struct attribute *f2fs_attrs[] = {
> ATTR_LIST(gc_segment_mode),
> ATTR_LIST(gc_reclaimed_segments),
> ATTR_LIST(max_atc_write_bio_size),
> + ATTR_LIST(max_atc_write_bio_entry_cnt),
> ATTR_LIST(max_fragment_chunk),
> ATTR_LIST(max_fragment_hole),
> ATTR_LIST(current_atomic_write),
next prev parent reply other threads:[~2026-10-17 2:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 11:49 [PATCH 1/5] f2fs: cache: introduce metadata_cache sysfs node Chao Yu
2026-10-07 11:49 ` [PATCH 2/5] f2fs: cache: shrink meta and node caches in f2fs_balance_fs_bg Chao Yu
2026-10-07 11:49 ` [PATCH 3/5] f2fs: cache: wake up f2fs_writeback when exceeding threshold Chao Yu
2026-10-07 11:49 ` [PATCH 4/5] f2fs: cache: support asynchronous write_end_io Chao Yu
2026-10-07 11:49 ` [PATCH 5/5] f2fs: introduce max_atc_write_bio_entry_cnt Chao Yu
2026-10-17 2:16 ` Chao Yu [this message]
2026-10-13 22:30 ` [f2fs-dev] [PATCH 1/5] f2fs: cache: introduce metadata_cache sysfs node patchwork-bot+f2fs
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=abeed257-b8d2-4c1d-9ee9-5e93f628348e@kernel.org \
--to=chao@kernel.org \
--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
all inboxes | Powered by JetHome®