From: Chen Feng <puck.chen@hisilicon.com>
To: Vladimir Davydov <vdavydov@virtuozzo.com>
Cc: 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: Tue, 28 Jun 2016 18:37:24 +0800 [thread overview]
Message-ID: <57725364.60307@hisilicon.com> (raw)
In-Reply-To: <20160627165723.GW21652@esperanza>
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.
>
OKi 1/4 ? 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.
>>
>> Currently, the shrinker nr_deferred is set to total_scan.
>> But it's not the real left of the shrinker.
>
> And it shouldn't. The idea behind nr_deferred is following. A shrinker
> may return SHRINK_STOP if the current allocation context doesn't allow
> to reclaim its objects (e.g. reclaiming inodes under GFP_NOFS is
> deadlock prone). In this case we can't call the shrinker right now, but
> if we just forget about the batch we are supposed to reclaim at the
> current iteration, we can wind up having too many of these objects so
> that they start to exert unfairly high pressure on user memory. So we
> add the amount that we wanted to scan but couldn't to nr_deferred, so
> that we can catch up when we get to shrink_slab() with a proper context.
>
I am confused with your comments. If the shrinker return STOP this time.
It also can return STOP next time.
Is there any other effects about this changei 1/4 ?
Any feedback is appreciated.
Thanks.
>> Change it to
>> the freeable - freed.
>>
>> Signed-off-by: Chen Feng <puck.chen@hisilicon.com>
>> ---
>> mm/vmscan.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/mm/vmscan.c b/mm/vmscan.c
>> index c4a2f45..1ce3fc4 100644
>> --- a/mm/vmscan.c
>> +++ b/mm/vmscan.c
>> @@ -357,8 +357,8 @@ static unsigned long do_shrink_slab(struct shrink_control *shrinkctl,
>> * manner that handles concurrent updates. If we exhausted the
>> * scan, there is no need to do an update.
>> */
>> - if (total_scan > 0)
>> - new_nr = atomic_long_add_return(total_scan,
>> + if (freeable - freed > 0)
>> + new_nr = atomic_long_add_return(freeable - freed,
>> &shrinker->nr_deferred[nid]);
>> else
>> new_nr = atomic_long_read(&shrinker->nr_deferred[nid]);
>
> --
> 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>
>
>
--
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:[~2016-06-28 10:38 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 [this message]
2016-06-28 16:48 ` Vladimir Davydov
2016-06-29 7:25 ` Minchan Kim
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=57725364.60307@hisilicon.com \
--to=puck.chen@hisilicon.com \
--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=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).