From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: zone: fix to avoid bio split on sequential zone
Date: Tue, 13 Oct 2026 22:30:41 +0000 [thread overview]
Message-ID: <179193064101.1493834.14246878856998575721.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261007101812.2348510-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 7 Oct 2026 10:18:12 +0000 you wrote:
> From: Chao Yu <chao@kernel.org>
>
> In the block layer, bio_split_to_limits() splits a bio if it exceeds
> any underlying queue limits:
> 1. queue_max_sectors: Splits bios larger than the transfer limit. This
> limit is set by the device driver/DMA controller (max_hw_sectors) and
> device-mapper targets. When flushing dirty pages (governed by VFS
> writeback_chunk_size() and f2fs nr_pages_to_skip()), f2fs merges
> contiguous pages into bios up to 512KB (1024 sectors) or more without
> checking queue_max_sectors, which will be split if the device or DM
> target enforces a smaller limit.
> 2. queue_max_segments: Splits bios exceeding scatter-gather segment
> limits. f2fs allocates bios with up to 256 pages, exceeding the
> 128-segment limit of DM targets (dm-default-key/dm-crypt) if pages
> are discontiguous.
> 3. chunk_sectors: Splits bios crossing chunk/zone boundaries. In f2fs,
> section_size strictly matches zone_size, and block allocation never
> spans across section boundaries, so bios never cross chunk_sectors.
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: zone: fix to avoid bio split on sequential zone
https://git.kernel.org/jaegeuk/f2fs/c/b9b036bd1e2c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-10-13 22:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 10:18 Chao Yu
2026-10-13 22:30 ` patchwork-bot+f2fs [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=179193064101.1493834.14246878856998575721.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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®