From: Chao Yu <chao@kernel.org>
To: Guowei Du <duguoweisz@gmail.com>, jaegeuk@kernel.org
Cc: linux-kernel@vger.kernel.org, duguowei <duguowei@xiaomi.com>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 7/7] f2fs: optimize shrink count
Date: Fri, 1 Jul 2022 08:50:02 +0800 [thread overview]
Message-ID: <a766299e-1a75-5293-dfeb-8f5d6c395644@kernel.org> (raw)
In-Reply-To: <20220630112629.6611-1-duguoweisz@gmail.com>
On 2022/6/30 19:26, Guowei Du wrote:
> From: duguowei <duguowei@xiaomi.com>
>
> Remove the local variable 'run_no', add comments for better
> reading.
Not sure, I guess original implementation considers the race condition for
f2fs_shrink_scan vs f2fs_shrink_scan case? so it uses a local variable to
keep the per-round context info?
Jaegeuk, please help to check that.
Thanks,
>
> Signed-off-by: duguowei <duguowei@xiaomi.com>
> ---
> fs/f2fs/shrinker.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/fs/f2fs/shrinker.c b/fs/f2fs/shrinker.c
> index dd3c3c7a90ec..7e439496dfca 100644
> --- a/fs/f2fs/shrinker.c
> +++ b/fs/f2fs/shrinker.c
> @@ -76,18 +76,18 @@ unsigned long f2fs_shrink_scan(struct shrinker *shrink,
> unsigned long nr = sc->nr_to_scan;
> struct f2fs_sb_info *sbi;
> struct list_head *p;
> - unsigned int run_no;
> unsigned long freed = 0;
>
> spin_lock(&f2fs_list_lock);
> - do {
> - run_no = ++shrinker_run_no;
> - } while (run_no == 0);
> + shrinker_run_no++;
> + /* if overflow, next loop needs to skip number 0 */
> + if (!shrinker_run_no)
> + shrinker_run_no = 1;
> p = f2fs_list.next;
> while (p != &f2fs_list) {
> sbi = list_entry(p, struct f2fs_sb_info, s_list);
>
> - if (sbi->shrinker_run_no == run_no)
> + if (sbi->shrinker_run_no == shrinker_run_no)
> break;
>
> /* stop f2fs_put_super */
> @@ -97,7 +97,7 @@ unsigned long f2fs_shrink_scan(struct shrinker *shrink,
> }
> spin_unlock(&f2fs_list_lock);
>
> - sbi->shrinker_run_no = run_no;
> + sbi->shrinker_run_no = shrinker_run_no;
>
> /* shrink extent cache entries */
> freed += f2fs_shrink_extent_tree(sbi, nr >> 1);
_______________________________________________
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:[~2022-07-01 0:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 11:26 [f2fs-dev] [PATCH 7/7] f2fs: optimize shrink count Guowei Du
2022-07-01 0:50 ` Chao Yu [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=a766299e-1a75-5293-dfeb-8f5d6c395644@kernel.org \
--to=chao@kernel.org \
--cc=duguowei@xiaomi.com \
--cc=duguoweisz@gmail.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.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).