From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Michal Hocko <mhocko@kernel.org>
Cc: "peter enderborg" <peter.enderborg@sonymobile.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
"Arve Hjønnevåg" <arve@android.com>,
"Riley Andrews" <riandrews@android.com>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
linux-mm@kvack.org
Subject: Re: [PATCH 1/3 staging-next] android: Collect statistics from lowmemorykiller
Date: Thu, 9 Feb 2017 21:07:37 +0100 [thread overview]
Message-ID: <20170209200737.GB11098@kroah.com> (raw)
In-Reply-To: <20170209192640.GC31906@dhcp22.suse.cz>
On Thu, Feb 09, 2017 at 08:26:41PM +0100, Michal Hocko wrote:
> On Thu 09-02-17 14:21:45, peter enderborg wrote:
> > This collects stats for shrinker calls and how much
> > waste work we do within the lowmemorykiller.
>
> This doesn't explain why do we need this information and who is going to
> use it. Not to mention it exports it in /proc which is considered a
> stable user API. This is a no-go, especially for something that is still
> lingering in the staging tree without any actuall effort to make it
> fully supported MM feature. I am actually strongly inclined to simply
> drop lmk from the tree completely.
I thought that someone was working to get the "native" mm features to
work properly with the lmk "feature" Do you recall if that work got
rejected, or just never happened?
thanks,
greg k-h
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-02-09 20:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 13:21 peter enderborg
2017-02-09 13:50 ` Greg Kroah-Hartman
2017-02-09 19:26 ` Michal Hocko
2017-02-09 20:07 ` Greg Kroah-Hartman [this message]
2017-02-09 20:54 ` Michal Hocko
2017-02-10 7:21 ` peter enderborg
2017-02-10 7:51 ` Greg Kroah-Hartman
2017-02-10 7:59 ` Michal Hocko
2017-02-10 9:05 ` peter enderborg
2017-02-10 9:15 ` Michal Hocko
2017-02-13 15:42 ` peter enderborg
2017-02-10 9:05 ` peter enderborg
2017-02-10 10:34 ` Greg Kroah-Hartman
2017-02-14 16:09 peter.enderborg
2017-02-14 16:50 ` Greg KH
2017-02-15 8:22 ` peter enderborg
2017-02-15 14:29 ` Greg KH
2017-02-14 16:51 ` Greg KH
2017-02-15 8:21 ` peter enderborg
2017-02-15 14:31 ` Greg KH
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=20170209200737.GB11098@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arve@android.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=peter.enderborg@sonymobile.com \
--cc=riandrews@android.com \
--cc=torvalds@linux-foundation.org \
/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