From: Minchan Kim <minchan@kernel.org>
To: Chen Feng <puck.chen@hisilicon.com>
Cc: Vladimir Davydov <vdavydov@virtuozzo.com>,
akpm@linux-foundation.org, hannes@cmpxchg.org, mhocko@suse.com,
vbabka@suse.cz, mgorman@techsingularity.net, riel@redhat.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
labbott@redhat.com, suzhuangluan@hisilicon.com,
oliver.fu@hisilicon.com, puck.chen@foxmail.com,
dan.zhao@hisilicon.com, saberlily.xia@hisilicon.com,
xuyiping@hisilicon.com
Subject: Re: [PATCH] mm, vmscan: set shrinker to the left page count
Date: Wed, 29 Jun 2016 16:25:24 +0900 [thread overview]
Message-ID: <20160629072524.GA18523@bbox> (raw)
In-Reply-To: <57725364.60307@hisilicon.com>
On Tue, Jun 28, 2016 at 06:37:24PM +0800, Chen Feng wrote:
> Thanks for you reply.
>
> On 2016/6/28 0:57, Vladimir Davydov wrote:
> > On Mon, Jun 27, 2016 at 07:02:15PM +0800, Chen Feng wrote:
> >> In my platform, there can be cache a lot of memory in
> >> ion page pool. When shrink memory the nr_to_scan to ion
> >> is always to little.
> >> to_scan: 395 ion_pool_cached: 27305
> >
> > That's OK. We want to shrink slabs gradually, not all at once.
> >
>
> OK， But my question there are a lot of memory waiting for free.
> But the to_scan is too little.
>
> So, the lowmemorykill may kill the wrong process.
So, the problem is LMK is too agressive. If it's really problem,
you could fix LMK to consider reclaimable slab as well as file
pages.
Thanks.
--
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:[~2016-06-29 7:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-27 11:02 [PATCH] mm, vmscan: set shrinker to the left page count Chen Feng
2016-06-27 16:57 ` Vladimir Davydov
2016-06-28 10:37 ` Chen Feng
2016-06-28 16:48 ` Vladimir Davydov
2016-06-29 7:25 ` Minchan Kim [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=20160629072524.GA18523@bbox \
--to=minchan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dan.zhao@hisilicon.com \
--cc=hannes@cmpxchg.org \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=oliver.fu@hisilicon.com \
--cc=puck.chen@foxmail.com \
--cc=puck.chen@hisilicon.com \
--cc=riel@redhat.com \
--cc=saberlily.xia@hisilicon.com \
--cc=suzhuangluan@hisilicon.com \
--cc=vbabka@suse.cz \
--cc=vdavydov@virtuozzo.com \
--cc=xuyiping@hisilicon.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;
as well as URLs for NNTP newsgroup(s).