[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YRZnMYCN1ArhM3wE@chrisdown.name>
Date: Fri, 13 Aug 2021 13:36:01 +0100
From: Chris Down <chris@...isdown.name>
To: yongw.pur@...il.com
Cc: tj@...nel.org, corbet@....net, akpm@...ux-foundation.org,
mhocko@...nel.org, vdavydov.dev@...il.com, tglx@...utronix.de,
peterz@...radead.org, shakeelb@...gle.com, guro@...com,
alexs@...nel.org, richard.weiyang@...il.com, sh_def@....com,
sfr@...b.auug.org.au, wang.yong12@....com.cn,
cgroups@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
yang.yang29@....com.cn
Subject: Re: [PATCH v1] mm: Add configuration to control whether vmpressure
notifier is enabled
yongw.pur@...il.com writes:
>From: wangyong <wang.yong12@....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.
Powered by blists - more mailing lists