From: Shakeel Butt <shakeelb@google.com>
To: yongw.pur@gmail.com
Cc: Tejun Heo <tj@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@kernel.org>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Roman Gushchin <guro@fb.com>,
alexs@kernel.org, Wei Yang <richard.weiyang@gmail.com>,
Hui Su <sh_def@163.com>, Stephen Rothwell <sfr@canb.auug.org.au>,
wang.yong12@zte.com.cn, Cgroups <cgroups@vger.kernel.org>,
linux-doc@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>,
yang.yang29@zte.com.cn, wangyong <wang.yong@zte.com.cn>
Subject: Re: [PATCH v2] mm: Add configuration to control whether vmpressure notifier is enabled
Date: Fri, 20 Aug 2021 04:42:07 -0700 [thread overview]
Message-ID: <CALvZod5usW9OEsJSbeGYBnSGVDNLLKqMoGAx-JQrX6s62r-XiA@mail.gmail.com> (raw)
In-Reply-To: <1629417219-74853-1-git-send-email-wang.yong12@zte.com.cn>
On Thu, Aug 19, 2021 at 4:54 PM <yongw.pur@gmail.com> wrote:
>
> From: wangyong <wang.yong@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.
>
It is also used by the networking stack to check memory pressure. See
mem_cgroup_under_socket_pressure().
next prev parent reply other threads:[~2021-08-20 11:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 23:53 yongw.pur
2021-08-20 11:26 ` Michal Hocko
2021-08-20 15:20 ` yong w
2021-08-20 15:41 ` Michal Hocko
2021-08-22 9:46 ` yong w
2021-08-30 13:49 ` Michal Hocko
2021-09-04 10:41 ` yong w
2021-09-06 6:37 ` Michal Hocko
2021-08-20 11:42 ` Shakeel Butt [this message]
2021-08-20 14:29 ` yong w
2021-08-22 10:06 ` 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=CALvZod5usW9OEsJSbeGYBnSGVDNLLKqMoGAx-JQrX6s62r-XiA@mail.gmail.com \
--to=shakeelb@google.com \
--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=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=vdavydov.dev@gmail.com \
--cc=wang.yong12@zte.com.cn \
--cc=wang.yong@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