From: Johannes Weiner <hannes@cmpxchg.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Roman Gushchin <guro@fb.com>,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"riel@surriel.com" <riel@surriel.com>,
"dchinner@redhat.com" <dchinner@redhat.com>,
"guroan@gmail.com" <guroan@gmail.com>,
Kernel Team <Kernel-team@fb.com>
Subject: Re: [LSF/MM TOPIC] dying memory cgroups and slab reclaim issues
Date: Wed, 20 Feb 2019 11:20:21 -0500 [thread overview]
Message-ID: <20190220162021.GB12866@cmpxchg.org> (raw)
In-Reply-To: <20190220072707.GB23020@dastard>
On Wed, Feb 20, 2019 at 06:27:07PM +1100, Dave Chinner wrote:
> freeable = 1
>
> ratio 4.15 priority 4.16 4.18 new
> 1:100 1 12 0 batch 1
> 1.32 1 9 0 batch 1
> 1:12 1 6 0 batch 1
> 1:6 1 3 0 batch 1
> 1:1 1 1 1 batch 1
> @@ -479,7 +479,16 @@ static unsigned long do_shrink_slab(struct shrink_control *shrinkctl,
>
> total_scan = nr;
> if (shrinker->seeks) {
> - delta = freeable >> priority;
> + /*
> + * Use a small non-zero offset for delta so that if the scan
> + * priority is low we always accumulate some pressure on caches
> + * that have few freeable objects in them. This allows light
> + * memory pressure to turn over caches with few freeable objects
> + * slowly without the need for memory pressure priority to wind
> + * up to the point where (freeable >> priority) is non-zero.
> + */
> + delta = ilog2(freeable);
The idea makes sense to me, but log2 fails us when freeable is
1. fls() should work, though.
> + delta += freeable >> priority;
> delta *= 4;
> do_div(delta, shrinker->seeks);
> } else {
next prev parent reply other threads:[~2019-02-20 16:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 7:13 [LSF/MM TOPIC] dying memory cgroups and slab reclaim issues Roman Gushchin
[not found] ` <20190219092323.GH4525@dhcp22.suse.cz>
2019-02-19 16:21 ` [LSF/MM ATTEND] MM track: dying memory cgroups and slab reclaim issue, memcg, THP Roman Gushchin
2019-02-20 2:47 ` [LSF/MM TOPIC] dying memory cgroups and slab reclaim issues Dave Chinner
2019-02-20 5:50 ` Dave Chinner
2019-02-20 7:27 ` Dave Chinner
2019-02-20 16:20 ` Johannes Weiner [this message]
2019-02-21 22:46 ` Roman Gushchin
2019-02-22 1:48 ` Rik van Riel
2019-02-22 1:57 ` Roman Gushchin
2019-02-28 20:30 ` Roman Gushchin
2019-02-28 21:30 ` Dave Chinner
2019-02-28 22:29 ` Roman Gushchin
-- strict thread matches above, loose matches on Subject: below --
2019-02-19 0:31 Roman Gushchin
2019-02-19 2:04 ` Dave Chinner
2019-02-19 17:31 ` Rik van Riel
2019-02-19 17:38 ` Michal Hocko
2019-02-19 23:26 ` Dave Chinner
2019-02-20 2:06 ` Rik van Riel
2019-02-20 4:33 ` Dave Chinner
2019-02-20 5:31 ` Roman Gushchin
2019-02-20 17:00 ` Rik van Riel
2019-02-18 23:53 Roman Gushchin
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=20190220162021.GB12866@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=Kernel-team@fb.com \
--cc=david@fromorbit.com \
--cc=dchinner@redhat.com \
--cc=guro@fb.com \
--cc=guroan@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=riel@surriel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.