From: patchwork-bot+f2fs@kernel.org
To: Sheng Yong <shengyong@oppo.com>
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
daehojeong@google.com, linux-kernel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH v3] f2fs: only fragment segment in the same section
Date: Mon, 15 Jul 2024 14:40:31 +0000 [thread overview]
Message-ID: <172105443178.17443.14567102589970622555.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240710012659.3415856-1-shengyong@oppo.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 10 Jul 2024 09:26:59 +0800 you wrote:
> When new_curseg() is allocating a new segment, if mode=fragment:xxx is
> switched on in large section scenario, __get_next_segno() will select
> the next segno randomly in the range of [0, maxsegno] in order to
> fragment segments.
>
> If the candidate segno is free, get_new_segment() will use it directly
> as the new segment.
>
> [...]
Here is the summary with links:
- [f2fs-dev,v3] f2fs: only fragment segment in the same section
https://git.kernel.org/jaegeuk/f2fs/c/e3a19972a49f
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: Sheng Yong <shengyong@oppo.com>
Cc: jaegeuk@kernel.org, chao@kernel.org, daehojeong@google.com,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v3] f2fs: only fragment segment in the same section
Date: Mon, 15 Jul 2024 14:40:31 +0000 [thread overview]
Message-ID: <172105443178.17443.14567102589970622555.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240710012659.3415856-1-shengyong@oppo.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 10 Jul 2024 09:26:59 +0800 you wrote:
> When new_curseg() is allocating a new segment, if mode=fragment:xxx is
> switched on in large section scenario, __get_next_segno() will select
> the next segno randomly in the range of [0, maxsegno] in order to
> fragment segments.
>
> If the candidate segno is free, get_new_segment() will use it directly
> as the new segment.
>
> [...]
Here is the summary with links:
- [f2fs-dev,v3] f2fs: only fragment segment in the same section
https://git.kernel.org/jaegeuk/f2fs/c/e3a19972a49f
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-07-15 14:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 1:26 [f2fs-dev] [PATCH v3] f2fs: only fragment segment in the same section Sheng Yong via Linux-f2fs-devel
2024-07-10 1:26 ` Sheng Yong
2024-07-15 14:40 ` patchwork-bot+f2fs [this message]
2024-07-15 14:40 ` [f2fs-dev] " patchwork-bot+f2fs
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=172105443178.17443.14567102589970622555.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=daehojeong@google.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=shengyong@oppo.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.