From: Chris Down <chris@chrisdown.name>
To: yongw.pur@gmail.com
Cc: tj@kernel.org, corbet@lwn.net, akpm@linux-foundation.org,
mhocko@kernel.org, vdavydov.dev@gmail.com, tglx@linutronix.de,
peterz@infradead.org, shakeelb@google.com, guro@fb.com,
alexs@kernel.org, richard.weiyang@gmail.com, sh_def@163.com,
sfr@canb.auug.org.au, wang.yong12@zte.com.cn,
cgroups@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
yang.yang29@zte.com.cn
Subject: Re: [PATCH v1] mm: Add configuration to control whether vmpressure notifier is enabled
Date: Fri, 13 Aug 2021 13:36:01 +0100 [thread overview]
Message-ID: <YRZnMYCN1ArhM3wE@chrisdown.name> (raw)
In-Reply-To: <1628855870-5070-1-git-send-email-wang.yong12@zte.com.cn>
yongw.pur@gmail.com writes:
>From: wangyong <wang.yong12@zte.com.cn>
>Inspired by PSI features, vmpressure inotifier function should also be
>configured to decide whether it is used, because it is an independent
>feature which notifies the user of memory pressure.
>
>Since the vmpressure interface is used in kernel common code, for
>users who do not use the vmpressure function, there will be
>additional overhead.
Could you please demonstrate this additional overhead with profiles or
demonstrations of other real world effects? Thanks.
next prev parent reply other threads:[~2021-08-13 12:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 11:57 yongw.pur
2021-08-13 12:36 ` Chris Down [this message]
2021-08-14 8:00 ` yong w
2021-08-13 13:09 ` Matthew Wilcox
2021-08-14 7:47 ` yong w
2021-08-13 13:43 ` Hu Haowen
2021-08-14 7:42 ` 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=YRZnMYCN1ArhM3wE@chrisdown.name \
--to=chris@chrisdown.name \
--cc=akpm@linux-foundation.org \
--cc=alexs@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=guro@fb.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=peterz@infradead.org \
--cc=richard.weiyang@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=sh_def@163.com \
--cc=shakeelb@google.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=vdavydov.dev@gmail.com \
--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