From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Chao Yu <chao@kernel.org>
Cc: xiuhong.wang@unisoc.com, jaegeuk@kernel.org,
zhiguo.niu@unisoc.com, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2 1/2] f2fs: fix to shrink read extent node in batches
Date: Sat, 23 Nov 2024 15:50:39 +0000 [thread overview]
Message-ID: <173237703949.3018181.7264272337903464166.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241122065005.3772987-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Fri, 22 Nov 2024 14:50:04 +0800 you wrote:
> We use rwlock to protect core structure data of extent tree during
> its shrink, however, if there is a huge number of extent nodes in
> extent tree, during shrink of extent tree, it may hold rwlock for
> a very long time, which may trigger kernel hang issue.
>
> This patch fixes to shrink read extent node in batches, so that,
> critical region of the rwlock can be shrunk to avoid its extreme
> long time hold.
>
> [...]
Here is the summary with links:
- [f2fs-dev,v2,1/2] f2fs: fix to shrink read extent node in batches
https://git.kernel.org/jaegeuk/f2fs/c/3fc5d5a182f6
- [f2fs-dev,v2,2/2] f2fs: add a sysfs node to limit max read extent count per-inode
https://git.kernel.org/jaegeuk/f2fs/c/009a8241a8e5
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
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, xiuhong.wang@unisoc.com,
zhiguo.niu@unisoc.com, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2 1/2] f2fs: fix to shrink read extent node in batches
Date: Sat, 23 Nov 2024 15:50:39 +0000 [thread overview]
Message-ID: <173237703949.3018181.7264272337903464166.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241122065005.3772987-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Fri, 22 Nov 2024 14:50:04 +0800 you wrote:
> We use rwlock to protect core structure data of extent tree during
> its shrink, however, if there is a huge number of extent nodes in
> extent tree, during shrink of extent tree, it may hold rwlock for
> a very long time, which may trigger kernel hang issue.
>
> This patch fixes to shrink read extent node in batches, so that,
> critical region of the rwlock can be shrunk to avoid its extreme
> long time hold.
>
> [...]
Here is the summary with links:
- [f2fs-dev,v2,1/2] f2fs: fix to shrink read extent node in batches
https://git.kernel.org/jaegeuk/f2fs/c/3fc5d5a182f6
- [f2fs-dev,v2,2/2] f2fs: add a sysfs node to limit max read extent count per-inode
https://git.kernel.org/jaegeuk/f2fs/c/009a8241a8e5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-11-23 15:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 6:50 [f2fs-dev] [PATCH v2 1/2] f2fs: fix to shrink read extent node in batches Chao Yu via Linux-f2fs-devel
2024-11-22 6:50 ` Chao Yu
2024-11-22 6:50 ` [f2fs-dev] [PATCH v2 2/2] f2fs: add a sysfs node to limit max read extent count per-inode Chao Yu via Linux-f2fs-devel
2024-11-22 6:50 ` Chao Yu
2024-11-23 15:50 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2024-11-23 15:50 ` [f2fs-dev] [PATCH v2 1/2] f2fs: fix to shrink read extent node in batches patchwork-bot+f2fs
2024-11-25 3:11 ` [f2fs-dev] 答复: " 王秀红 (Xiuhong Wang)
2024-11-25 3:11 ` 王秀红 (Xiuhong Wang)
2024-11-25 11:13 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2024-11-25 11:13 ` Chao Yu
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=173237703949.3018181.7264272337903464166.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@kernel.org \
--cc=xiuhong.wang@unisoc.com \
--cc=zhiguo.niu@unisoc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.