From: Andrew Morton <akpm@linux-foundation.org>
To: "Guilherme G. Piccoli" <gpiccoli@canonical.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
gavin.guo@canonical.com, kernel@gpiccoli.net,
Mel Gorman <mgorman@techsingularity.net>
Subject: Re: [PATCH] mm, compaction: Indicate when compaction is manually triggered by sysctl
Date: Thu, 7 May 2020 16:04:38 -0700 [thread overview]
Message-ID: <20200507160438.ed336a1e00c23c6863d75ae5@linux-foundation.org> (raw)
In-Reply-To: <20200507215946.22589-1-gpiccoli@canonical.com>
On Thu, 7 May 2020 18:59:46 -0300 "Guilherme G. Piccoli" <gpiccoli@canonical.com> wrote:
> Currently we have no way to determine if compaction was triggered
> by sysctl write, but this is an interesting information to have,
> specially in systems with high uptime that presents lots of
> fragmented memory. There's no statistic indicating if compaction
> was triggered manually or ran by Linux itself, the vmstat numbers
> cannot tell the user this information.
Could add it to vmstat?
> This patch adds a very simple message to kernel log when compaction
> is requested through a write to sysctl file, and also it accumulates
> the number of previously manual compaction executions. It follows
> the approach used by drop_caches.
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...
next prev parent reply other threads:[~2020-05-07 23:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 21:59 [PATCH] mm, compaction: Indicate when compaction is manually triggered by sysctl Guilherme G. Piccoli
2020-05-07 23:04 ` Andrew Morton [this message]
2020-05-08 2:14 ` Guilherme G. Piccoli
2020-05-08 18:31 ` David Rientjes
2020-05-08 19:01 ` Guilherme Piccoli
2020-05-11 1:24 ` David Rientjes
2020-05-11 11:26 ` Guilherme Piccoli
2020-05-18 7:06 ` peter enderborg
2020-05-18 12:14 ` Guilherme Piccoli
2020-05-18 12:54 ` Enderborg, Peter
2020-05-18 13:50 ` Guilherme Piccoli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200507160438.ed336a1e00c23c6863d75ae5@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=gavin.guo@canonical.com \
--cc=gpiccoli@canonical.com \
--cc=kernel@gpiccoli.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).