From: Michal Hocko <mhocko@kernel.org>
To: peter enderborg <peter.enderborg@sonymobile.com>
Cc: devel@driverdev.osuosl.org,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.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 0/3 staging-next] android: Lowmemmorykiller task tree
Date: Mon, 20 Feb 2017 11:21:22 +0100 [thread overview]
Message-ID: <20170220102121.GF2431@dhcp22.suse.cz> (raw)
In-Reply-To: <5579dead-092d-2ce2-a9d4-f2b50721f0dc@sonymobile.com>
On Mon 13-02-17 16:42:42, peter enderborg wrote:
> On 02/10/2017 11:27 AM, Michal Hocko wrote:
> > [I have only now see this cover - it answers some of the questions I've
> > had to specific patches. It would be really great if you could use git
> > send-email to post patch series - it just does the right thing(tm)]
> >
> > On Thu 09-02-17 14:21:40, peter enderborg wrote:
> >> Lowmemorykiller efficiency problem and a solution.
> >>
> >> Lowmemorykiller in android has a severe efficiency problem. The basic
> >> problem is that the registered shrinker gets called very often without
> >> anything actually happening.
> > Which is an inherent problem because lkml doesn't belong to shrinkers
> > infrastructure.
>
> Not really what this patch address. I see it as a problem with shrinker
> that there no slow-path-free (scan/count) where it should belong.
> This patch address a specific problem where lot of cpu are wasted
> in low memory conditions.
Let me repeat. The specific problem you are trying to solve is
_inherent_ to how the lmk is designed. Full stop.
--
Michal Hocko
SUSE Labs
--
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>
prev parent reply other threads:[~2017-02-20 10:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 13:21 [PATCH 0/3 staging-next] android: Lowmemmorykiller task tree peter enderborg
2017-02-09 15:42 ` [PATCH 1/3 v2 staging-next] android: Collect statistics from lowmemorykiller peter enderborg
2017-02-09 20:13 ` Greg Kroah-Hartman
2017-02-10 7:12 ` peter enderborg
2017-02-10 10:27 ` [PATCH 0/3 staging-next] android: Lowmemmorykiller task tree Michal Hocko
2017-02-13 15:42 ` peter enderborg
2017-02-20 10:21 ` Michal Hocko [this message]
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=20170220102121.GF2431@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=arve@android.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).