linux-kernel - Re: [PATCH v1] mm: Add configuration to control whether vmpressure notifier is enabled

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Sat, 14 Aug 2021 16:00:59 +0800
From:   yong w <yongw.pur@...il.com>
To:     Chris Down <chris@...isdown.name>
Cc:     tj@...nel.org, corbet@....net, akpm@...ux-foundation.org,
        mhocko@...nel.org, vdavydov.dev@...il.com, tglx@...utronix.de,
        peterz@...radead.org, Shakeel Butt <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

Chris Down <chris@...isdown.name> 于2021年8月13日周五 下午8:36写道：
>
> 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.

Thanks for your reply. In terms of code, it will reduce the operation
of some code.

To  demonstrate this additional overhead, It is planned to use lmbench and
Christoph Lamenter’s pagefault tool  (https://lkml.org/lkml/2006/8/29/294)
for comparative testing.

Thanks.