linux-kernel - Re: [PATCH] mm, compaction: Indicate when compaction is manually triggered by sysctl

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:   Thu, 7 May 2020 23:14:10 -0300
From:   "Guilherme G. Piccoli" <kernel@...ccoli.net>
To:     Andrew Morton <akpm@...ux-foundation.org>
Cc:     "Guilherme G. Piccoli" <gpiccoli@...onical.com>,
        linux-mm@...ck.org, linux-kernel@...r.kernel.org,
        Gavin Guo <gavin.guo@...onical.com>,
        Mel Gorman <mgorman@...hsingularity.net>
Subject: Re: [PATCH] mm, compaction: Indicate when compaction is manually
 triggered by sysctl

On Thu, May 7, 2020 at 8:04 PM Andrew Morton <akpm@...ux-foundation.org> wrote:
>
> Could add it to vmstat?

Hi Andrew, thanks for your suggestion! I thought the same, as a second
potential solution for this..was planning to add as a comment below
the "---" but forgot heheh
I agree that would be great in vmstat, do you have a name suggestion
for it? "compaction_triggered" maybe?


> Userspace could write to /dev/kmsg when it decides to trigger
> compaction?  Although using the kernel log seems a fairly lame way for
> userspace to record its own actions...
Well...you can think that the problem we are trying to solve was more
like...admin forgot if they triggered or not the compaction hehe
So, counting on the user to keep track of it is what I'd like to
avoid. And thinking about drop_caches (that have an indication when
triggered) makes me think this indeed does make sense for compaction
too.
Cheers,

Guilherme