From: Chao Yu <chao@kernel.org>
To: Jakob Koschel <jakobkoschel@gmail.com>, Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org, "Bos, H.J." <h.j.bos@vu.nl>,
Brian Johannesmeyer <bjohannesmeyer@gmail.com>,
Cristiano Giuffrida <c.giuffrida@vu.nl>,
linux-f2fs-devel@lists.sourceforge.net,
Mike Rapoport <rppt@kernel.org>
Subject: Re: [f2fs-dev] [PATCH 1/2] f2fs: use separate list iterator variable to call list_move_tail()
Date: Tue, 12 Apr 2022 17:40:27 +0800 [thread overview]
Message-ID: <4d54f494-b143-8885-a31e-924a83409e2d@kernel.org> (raw)
In-Reply-To: <20220331221650.891790-1-jakobkoschel@gmail.com>
On 2022/4/1 6:16, Jakob Koschel wrote:
> In preparation to limit the scope of a list iterator to the list
> traversal loop, use a dedicated pointer to point to the found element
> [1].
>
> If no break is hit or the list is empty, 'next' will be NULL and
> list_move_tail() should be called explicitly on the head directly.
>
> Link: https://lore.kernel.org/all/CAHk-=wgRr_D8CB-D9Kg-c=EHreAsk5SqXPwr9Y7k9sA6cWXJ6w@mail.gmail.com/
> Signed-off-by: Jakob Koschel <jakobkoschel@gmail.com>
> ---
> fs/f2fs/segment.c | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
> index 22dfeb991529..81ef2c3d08e5 100644
> --- a/fs/f2fs/segment.c
> +++ b/fs/f2fs/segment.c
> @@ -4175,16 +4175,20 @@ static void release_sit_entry_set(struct sit_entry_set *ses)
> static void adjust_sit_entry_set(struct sit_entry_set *ses,
> struct list_head *head)
> {
> - struct sit_entry_set *next = ses;
> + struct sit_entry_set *next = NULL, *iter = ses;
>
> if (list_is_last(&ses->set_list, head))
> return;
>
> - list_for_each_entry_continue(next, head, set_list)
> - if (ses->entry_cnt <= next->entry_cnt)
> + list_for_each_entry_continue(iter, head, set_list)
> + if (ses->entry_cnt <= iter->entry_cnt) {
> + next = iter;
> + list_move_tail(&ses->set_list, &iter->set_list);
> break;
return;
> + }
>
> - list_move_tail(&ses->set_list, &next->set_list);
> + if (!next)
> + list_move_tail(&ses->set_list, head);
list_move_tail(&ses->set_list, head);
Then we don't need @next variable, right?
Thanks,
> }
>
> static void add_sit_entry(unsigned int segno, struct list_head *head)
>
> base-commit: d888c83fcec75194a8a48ccd283953bdba7b2550
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2022-04-12 9:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 22:16 [f2fs-dev] [PATCH 1/2] f2fs: use separate list iterator variable to call list_move_tail() Jakob Koschel
2022-03-31 22:16 ` [f2fs-dev] [PATCH 2/2] f2fs: replace usage of found with dedicated list iterator variable Jakob Koschel
2022-04-12 9:41 ` Chao Yu
2022-04-12 9:40 ` Chao Yu [this message]
2022-04-12 11:02 ` [f2fs-dev] [PATCH 1/2] f2fs: use separate list iterator variable to call list_move_tail() Jakob Koschel
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=4d54f494-b143-8885-a31e-924a83409e2d@kernel.org \
--to=chao@kernel.org \
--cc=bjohannesmeyer@gmail.com \
--cc=c.giuffrida@vu.nl \
--cc=h.j.bos@vu.nl \
--cc=jaegeuk@kernel.org \
--cc=jakobkoschel@gmail.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rppt@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).