linux-kernel - Re: [PATCH V2 5/7] mm: add vmstat account for MADV

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

Date:   Fri, 10 Feb 2017 09:50:15 -0800
From:   Shaohua Li <shli@...com>
To:     Michal Hocko <mhocko@...nel.org>
CC:     <linux-kernel@...r.kernel.org>, <linux-mm@...ck.org>,
        <Kernel-team@...com>, <danielmicay@...il.com>,
        <minchan@...nel.org>, <hughd@...gle.com>, <hannes@...xchg.org>,
        <riel@...hat.com>, <mgorman@...hsingularity.net>,
        <akpm@...ux-foundation.org>
Subject: Re: [PATCH V2 5/7] mm: add vmstat account for MADV_FREE pages

On Fri, Feb 10, 2017 at 02:27:27PM +0100, Michal Hocko wrote:
> On Fri 03-02-17 15:33:21, Shaohua Li wrote:
> > Show MADV_FREE pages info in proc/sysfs files.
> 
> How are we going to use this information? Why it isn't sufficient to
> watch for lazyfree events? I mean this adds quite some code and it is
> not clear (at least from the changelog) we we need this information.

It's just like any other meminfo we added to let user know what happens in the
system. Users can use the info for monitoring/diagnosing. the
lazyfree/lazyfreed events can't reflect the lazyfree page info because
'lazyfree - lazyfreed' doesn't equal current lazyfree pages and the events
aren't per-node. I'll add more description in the changelog.

Thanks,
Shaohua