mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+f2fs@kernel.org
To: Huang Jianan <huangjianan@xiaomi.com>
Cc: linux-f2fs-devel@lists.sourceforge.net, chao@kernel.org,
	jaegeuk@kernel.org, shengyong1@xiaomi.com,
	linux-kernel@vger.kernel.org, wanghui33@xiaomi.com
Subject: Re: [f2fs-dev] [PATCH v4] f2fs: avoid splitting bio when reading multiple pages
Date: Wed, 09 Jul 2025 18:10:09 +0000	[thread overview]
Message-ID: <175208460952.806926.13620512272731608715.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250630125753.650630-1-huangjianan@xiaomi.com>

Hello:

This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:

On Mon, 30 Jun 2025 20:57:53 +0800 you wrote:
> When fewer pages are read, nr_pages may be smaller than nr_cpages. Due
> to the nr_vecs limit, the compressed pages will be split into multiple
> bios and then merged at the block level. In this case, nr_cpages should
> be used to pre-allocate bvecs.
> To handle this case, align max_nr_pages to cluster_size, which should be
> enough for all compressed pages.
> 
> [...]

Here is the summary with links:
  - [f2fs-dev,v4] f2fs: avoid splitting bio when reading multiple pages
    https://git.kernel.org/jaegeuk/f2fs/c/185f203a6991

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-07-09 18:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-30 12:57 Jianan Huang
2025-07-01  3:01 ` Chao Yu
2025-07-09 18:10 ` 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=175208460952.806926.13620512272731608715.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+f2fs@kernel.org \
    --cc=chao@kernel.org \
    --cc=huangjianan@xiaomi.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shengyong1@xiaomi.com \
    --cc=wanghui33@xiaomi.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®