From: Yuwei Guan <ssawgyw@gmail.com>
To: Chao Yu <chao@kernel.org>, jaegeuk@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: do decrease_sleep_time() if any of the victims have been selected
Date: Sun, 11 Dec 2022 20:30:12 +0800 [thread overview]
Message-ID: <3b51e6ae-5df5-60c4-3261-557b44e34291@gmail.com> (raw)
In-Reply-To: <810bd221-1f35-db79-e9f3-a521464b3eaf@kernel.org>
在 2022/12/11 10:52, Chao Yu 写道:
> On 2022/12/9 19:28, Yuwei Guan wrote:
>> In non-foreground gc mode, if no victim is selected, the gc process
>> will wait for no_gc_sleep_time before waking up again. In this
>> subsequent time, even though a victim will be selected, the gc process
>> still waits for no_gc_sleep_time before waking up. The configuration
>> of wait_ms is not reasonable.
>>
>> After any of the victims have been selected, we need to do
>> decrease_sleep_time() to reduce wait_ms.
>>
>> If it is GC_URGENT_HIGH or GC_URGENT_MID gc mode,
>> wait_ms will keep urgent_sleep_time after executing
>> decrease_sleep_time().
>>
>> In decrease_sleep_time() wait_time will be reduced to max_sleep_time
>> from no_gc_sleep_time, if *wait is no_gc_sleep_time. And then it goes
>> down in the next step.
>>
>> Signed-off-by: Yuwei Guan <Yuwei.Guan@zeekrlife.com>
>> ---
>> fs/f2fs/gc.c | 2 ++
>> fs/f2fs/gc.h | 7 ++++++-
>> 2 files changed, 8 insertions(+), 1 deletion(-)
>>
>> diff --git a/fs/f2fs/gc.c b/fs/f2fs/gc.c
>> index f0c6506d8975..c023ffeb9268 100644
>> --- a/fs/f2fs/gc.c
>> +++ b/fs/f2fs/gc.c
>> @@ -141,6 +141,8 @@ static int gc_thread_func(void *data)
>> /* don't bother wait_ms by foreground gc */
>> if (!foreground)
>> wait_ms = gc_th->no_gc_sleep_time;
>> + } else {
>> + decrease_sleep_time(gc_th, &wait_ms);
>
> Once BGGC selects valid victim, it will go faster and fater?
> > How about:
>
> } else {
> /* reset wait_ms to default sleep time */
> if (wait_ms == gc_th->no_gc_sleep_time)
> wait_ms = gc_th->min_sleep_time;
> }
Indeed. it will go faster and fater, until wait_ms reduces to
min_sleep_time. But your suggestion seems more reasonable, I will send
it in v2 patch.
>
> Thanks,
>
>> }
>> if (foreground)
>> diff --git a/fs/f2fs/gc.h b/fs/f2fs/gc.h
>> index 19b956c2d697..6402584dcd72 100644
>> --- a/fs/f2fs/gc.h
>> +++ b/fs/f2fs/gc.h
>> @@ -150,8 +150,13 @@ static inline void decrease_sleep_time(struct
>> f2fs_gc_kthread *gc_th,
>> {
>> unsigned int min_time = gc_th->min_sleep_time;
>> - if (*wait == gc_th->no_gc_sleep_time)
>> + if (*wait == gc_th->urgent_sleep_time)
>> + return;
>> +
>> + if (*wait == gc_th->no_gc_sleep_time) {
>> *wait = gc_th->max_sleep_time;
>> + return;
>> + }
>> if ((long long)*wait - (long long)min_time < (long long)min_time)
>> *wait = min_time;
_______________________________________________
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-12-11 12:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 11:28 [f2fs-dev] [PATCH] f2fs: do decrease_sleep_time() if any of the victims have been selected Yuwei Guan
2022-12-11 2:52 ` Chao Yu
2022-12-11 12:30 ` Yuwei Guan [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=3b51e6ae-5df5-60c4-3261-557b44e34291@gmail.com \
--to=ssawgyw@gmail.com \
--cc=chao@kernel.org \
--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).