From: Rik van Riel <riel@redhat.com>
To: Vaibhav Shinde <v.bhav.shinde@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mgorman@suse.de>
Subject: Re: kswapd hogging in lowmem_shrink
Date: Fri, 13 Mar 2015 10:52:44 -0400 [thread overview]
Message-ID: <5502F9BC.2020001@redhat.com> (raw)
In-Reply-To: <CAB5gotvwyD74UugjB6XQ_v=o11Hu9wAuA6N94UvGObPARYEz0w@mail.gmail.com>
On 03/13/2015 10:25 AM, Vaibhav Shinde wrote:
>
> On low memory situation, I see various shrinkers being invoked, but in
> lowmem_shrink() case, kswapd is found to be hogging for around 150msecs.
>
> Due to this my application suffer latency issue, as the cpu was not
> released by kswapd0.
>
> I took below traces with vmscan events, that show lowmem_shrink taking
> such long time for execution.
This is the Android low memory killer, which kills the
task with the lowest priority in the system.
The low memory killer will iterate over all the tasks
in the system to identify the task to kill.
This is not a problem in Android systems, and other
small systems where this piece of code is used.
What kind of system are you trying to use the low
memory killer on?
How many tasks are you running?
--
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:[~2015-03-13 14:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 14:25 Vaibhav Shinde
2015-03-13 14:52 ` Rik van Riel [this message]
2015-03-13 15:27 ` Vaibhav Shinde
2015-03-16 7:45 ` Vaibhav Shinde
2015-03-16 11:43 ` Rik van Riel
2015-03-13 15:23 ` Michal Hocko
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=5502F9BC.2020001@redhat.com \
--to=riel@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=v.bhav.shinde@gmail.com \
/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