From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Marco Elver <elver@google.com>, <akpm@linux-foundation.org>
Cc: <glider@google.com>, <dvyukov@google.com>, <jannh@google.com>,
<mark.rutland@arm.com>, <linux-kernel@vger.kernel.org>,
<linux-mm@kvack.org>, <kasan-dev@googlegroups.com>,
<hdanton@sina.com>
Subject: Re: [PATCH v2 2/3] kfence: maximize allocation wait timeout duration
Date: Thu, 16 Sep 2021 09:02:27 +0800 [thread overview]
Message-ID: <6c0d5f40-5067-3a59-65fa-6977b6f70219@huawei.com> (raw)
In-Reply-To: <20210421105132.3965998-3-elver@google.com>
On 2021/4/21 18:51, Marco Elver wrote:
> The allocation wait timeout was initially added because of warnings due
> to CONFIG_DETECT_HUNG_TASK=y [1]. While the 1 sec timeout is sufficient
> to resolve the warnings (given the hung task timeout must be 1 sec or
> larger) it may cause unnecessary wake-ups if the system is idle.
> [1] https://lkml.kernel.org/r/CADYN=9J0DQhizAGB0-jz4HOBBh+05kMBXb4c0cXMS7Qi5NAJiw@mail.gmail.com
>
> Fix it by computing the timeout duration in terms of the current
> sysctl_hung_task_timeout_secs value.
>
> Signed-off-by: Marco Elver <elver@google.com>
> ---
> mm/kfence/core.c | 12 +++++++++++-
> 1 file changed, 11 insertions(+), 1 deletion(-)
>
> diff --git a/mm/kfence/core.c b/mm/kfence/core.c
> index 235d726f88bc..9742649f3f88 100644
> --- a/mm/kfence/core.c
> +++ b/mm/kfence/core.c
> @@ -20,6 +20,7 @@
> #include <linux/moduleparam.h>
> #include <linux/random.h>
> #include <linux/rcupdate.h>
> +#include <linux/sched/sysctl.h>
> #include <linux/seq_file.h>
> #include <linux/slab.h>
> #include <linux/spinlock.h>
> @@ -621,7 +622,16 @@ static void toggle_allocation_gate(struct work_struct *work)
> /* Enable static key, and await allocation to happen. */
> static_branch_enable(&kfence_allocation_key);
>
> - wait_event_timeout(allocation_wait, atomic_read(&kfence_allocation_gate), HZ);
> + if (sysctl_hung_task_timeout_secs) {
> + /*
> + * During low activity with no allocations we might wait a
> + * while; let's avoid the hung task warning.
> + */
> + wait_event_timeout(allocation_wait, atomic_read(&kfence_allocation_gate),
> + sysctl_hung_task_timeout_secs * HZ / 2);
> + } else {
> + wait_event(allocation_wait, atomic_read(&kfence_allocation_gate));
> + }
>
> /* Disable static key and reset timer. */
> static_branch_disable(&kfence_allocation_key);
next prev parent reply other threads:[~2021-09-16 1:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 10:51 [PATCH v2 0/3] kfence: optimize timer scheduling Marco Elver
2021-04-21 10:51 ` [PATCH v2 1/3] kfence: await for allocation using wait_event Marco Elver
2021-04-21 10:51 ` [PATCH v2 2/3] kfence: maximize allocation wait timeout duration Marco Elver
2021-09-16 1:02 ` Kefeng Wang [this message]
2021-09-16 1:20 ` Kefeng Wang
2021-09-16 8:49 ` Marco Elver
2021-09-18 8:07 ` Liu Shixin
2021-09-18 9:37 ` Marco Elver
2021-09-18 9:45 ` Marco Elver
2021-09-16 15:45 ` David Laight
2021-09-16 15:48 ` Marco Elver
2021-04-21 10:51 ` [PATCH v2 3/3] kfence: use power-efficient work queue to run delayed work Marco Elver
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=6c0d5f40-5067-3a59-65fa-6977b6f70219@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=hdanton@sina.com \
--cc=jannh@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox