From: Chris Down <chris@chrisdown.name>
To: yongw.pur@gmail.com
Cc: tj@kernel.org, mhocko@suse.com, peterz@infradead.org,
wang.yong12@zte.com.cn, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
yang.yang29@zte.com.cn
Subject: Re: [PATCH v2] vmpressure: wake up work only when there is registration event
Date: Tue, 14 Sep 2021 17:49:06 +0100 [thread overview]
Message-ID: <YUDSgr+iwVz7iFBN@chrisdown.name> (raw)
In-Reply-To: <1631635551-8583-1-git-send-email-wang.yong12@zte.com.cn>
yongw.pur@gmail.com writes:
>From: wangyong <wang.yong12@zte.com.cn>
>
>Use the global variable num_events to record the number of vmpressure
>events registered by the system, and wake up work only when there is
>registration event.
>Usually, the vmpressure event is not registered in the system, this patch
>can avoid waking up work and doing nothing.
>
>Test with 5.14.0-rc5-next-20210813 on x86_64 4G ram.
>Consume cgroup memory until it is about to be reclaimed, then execute
>"perf stat -I 2000 malloc.out" command to trigger memory reclamation
>and get performance results.
>The context-switches is reduced by about 20 times.
>
>unpatched:
>Average of 10 test results
>582.4674048 task-clock(msec)
>19910.8 context-switches
>0 cpu-migrations
>1292.9 page-faults
>414784733.1 cycles
><not supported> stalled-cycles-frontend
><not supported> stalled-cycles-backend
>580070698.4 instructions
>125572244.7 branches
>2073541.2 branch-misses
>
>patched
>Average of 10 test results
>973.6174796 task-clock(msec)
>988.6 context-switches
>0 cpu-migrations
>1785.2 page-faults
>772883602.4 cycles
><not supported> stalled-cycles-frontend
><not supported> stalled-cycles-backend
>1360280911 instructions
>290519434.9 branches
>3378378.2 branch-misses
>
>Tested-by: Zeal Robot <zealci@zte.com.cn>
That's not how Tested-by works. Tested-by is for human testers who have
actively understand and have validated the effects of the code, not CI: please
remove the tag.
>Signed-off-by: wangyong <wang.yong12@zte.com.cn>
>---
>
>Changes since v1:
>-Use static_key type data as global variable
>-Make event registration judgment earlier
>
> mm/vmpressure.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
>diff --git a/mm/vmpressure.c b/mm/vmpressure.c
>index 76518e4..6f4e984 100644
>--- a/mm/vmpressure.c
>+++ b/mm/vmpressure.c
>@@ -67,6 +67,11 @@ static const unsigned int vmpressure_level_critical = 95;
> */
> static const unsigned int vmpressure_level_critical_prio = ilog2(100 / 10);
>
>+/*
>+ * Count the number of vmpressure events registered in the system.
>+ */
>+DEFINE_STATIC_KEY_FALSE(num_events);
>+
> static struct vmpressure *work_to_vmpressure(struct work_struct *work)
> {
> return container_of(work, struct vmpressure, work);
>@@ -272,6 +277,9 @@ void vmpressure(gfp_t gfp, struct mem_cgroup *memcg, bool tree,
> return;
>
> if (tree) {
>+ if (!static_branch_unlikely(&num_events))
>+ return;
>+
> spin_lock(&vmpr->sr_lock);
> scanned = vmpr->tree_scanned += scanned;
> vmpr->tree_reclaimed += reclaimed;
>@@ -407,6 +415,7 @@ int vmpressure_register_event(struct mem_cgroup *memcg,
> mutex_lock(&vmpr->events_lock);
> list_add(&ev->node, &vmpr->events);
> mutex_unlock(&vmpr->events_lock);
>+ static_branch_inc(&num_events);
> ret = 0;
> out:
> kfree(spec_orig);
>@@ -435,6 +444,7 @@ void vmpressure_unregister_event(struct mem_cgroup *memcg,
> if (ev->efd != eventfd)
> continue;
> list_del(&ev->node);
>+ static_branch_dec(&num_events);
> kfree(ev);
> break;
> }
>--
>2.7.4
>
>
next prev parent reply other threads:[~2021-09-14 16:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 16:05 yongw.pur
2021-09-14 16:49 ` Chris Down [this message]
2021-09-15 12:42 ` Michal Hocko
2021-09-17 15:38 ` yong w
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=YUDSgr+iwVz7iFBN@chrisdown.name \
--to=chris@chrisdown.name \
--cc=cgroups@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=peterz@infradead.org \
--cc=tj@kernel.org \
--cc=wang.yong12@zte.com.cn \
--cc=yang.yang29@zte.com.cn \
--cc=yongw.pur@gmail.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