linux-kernel - Re: [PATCH v3] mm: add thp_utilization metrics to /proc/thp

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>] [day] [month] [year] [list]

Message-ID: <70BEF411-33A1-4733-AE09-BE8486D2F8E8@oracle.com>
Date:   Fri, 5 Aug 2022 20:28:19 +0000
From:   William Kucharski <william.kucharski@...cle.com>
To:     "alexlzhu@...com" <alexlzhu@...com>
CC:     "linux-mm@...ck.org" <linux-mm@...ck.org>,
        "kernel-team@...com" <kernel-team@...com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "akpm@...ux-foundation.org" <akpm@...ux-foundation.org>
Subject: Re: [PATCH v3] mm: add thp_utilization metrics to
 /proc/thp_utilization

> On Aug 5, 2022, at 12:40, alexlzhu@...com wrote:
> 
> From: Alexander Zhu <alexlzhu@...com>
> 
> This change introduces a tool that scans through all of physical
> memory for anonymous THPs and groups them into buckets based
> on utilization.

Out of curiosity, do you have any statistics on how much of a performance impact scanning may have?

We've reached the point where we've finally been able to show previous admonitions to not enable THP due to a negative performance impact no longer hold true, and I'd hate to see systems on which enabling THP now would cause a performance hit due to this scanner.