From: patchwork-bot+f2fs@kernel.org
To: Jiucheng Xu <jiucheng.xu@amlogic.com>
Cc: jaegeuk@kernel.org, chao@kernel.org,
devnull+jiucheng.xu.amlogic.com@kernel.org,
tuan.zhang@amlogic.com, linux-kernel@vger.kernel.org,
jianxin.pan@amlogic.com, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: Use mapping->gfp_mask to get file cache for writing
Date: Tue, 11 Nov 2025 22:50:30 +0000 [thread overview]
Message-ID: <176290143023.3596344.4932276486991628363.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251010-origin-dev-v2-1-952a3c98cd9c@amlogic.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Fri, 10 Oct 2025 10:45:50 +0000 you wrote:
> From: Jiucheng Xu <jiucheng.xu@amlogic.com>
>
> On 32-bit architectures, when GFP_NOFS is used, the file cache for write
> operations cannot be allocated from the highmem and CMA.
>
> Since mapping->gfp_mask is set to GFP_HIGHUSER_MOVABLE during inode
> allocation, using mapping_gfp_mask(mapping) as the GFP flag of getting file
> cache for writing is more efficient for 32-bit architectures.
>
> [...]
Here is the summary with links:
- [f2fs-dev,v2] f2fs: Use mapping->gfp_mask to get file cache for writing
https://git.kernel.org/jaegeuk/f2fs/c/2308de27c03d
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:[~2025-11-11 22:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 10:45 [PATCH v2] f2fs: Use mapping->gfp_mask to get file cache for writing Jiucheng Xu via B4 Relay
2025-10-10 11:22 ` Chao Yu
2025-11-11 22:50 ` 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=176290143023.3596344.4932276486991628363.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=devnull+jiucheng.xu.amlogic.com@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=jianxin.pan@amlogic.com \
--cc=jiucheng.xu@amlogic.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tuan.zhang@amlogic.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