From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: nathan@kernel.org, jaegeuk@kernel.org,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v3] f2fs: reduce stack memory cost by using bitfield in struct f2fs_io_info
Date: Mon, 06 Feb 2023 03:40:19 +0000 [thread overview]
Message-ID: <167565481942.5323.508420128518769085.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230202070456.3497513-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Thu, 2 Feb 2023 15:04:56 +0800 you wrote:
> This patch tries to use bitfield in struct f2fs_io_info to improve
> memory usage.
>
> struct f2fs_io_info {
> ...
> unsigned int need_lock:8; /* indicate we need to lock cp_rwsem */
> unsigned int version:8; /* version of the node */
> unsigned int submitted:1; /* indicate IO submission */
> unsigned int in_list:1; /* indicate fio is in io_list */
> unsigned int is_por:1; /* indicate IO is from recovery or not */
> unsigned int retry:1; /* need to reallocate block address */
> unsigned int encrypted:1; /* indicate file is encrypted */
> unsigned int post_read:1; /* require post read */
> ...
> };
>
> [...]
Here is the summary with links:
- [f2fs-dev,v3] f2fs: reduce stack memory cost by using bitfield in struct f2fs_io_info
https://git.kernel.org/jaegeuk/f2fs/c/2eae077e6e46
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2023-02-06 3:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 7:04 [f2fs-dev] [PATCH v3] f2fs: reduce stack memory cost by using bitfield in struct f2fs_io_info Chao Yu
2023-02-06 3:40 ` 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=167565481942.5323.508420128518769085.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=nathan@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;
as well as URLs for NNTP newsgroup(s).