From: Michal Hocko <mhocko@suse.cz>
To: Roman Gushchin <klamm@yandex-team.ru>
Cc: Johannes Weiner-Arquette <hannes@cmpxchg.org>,
"bsingharora@gmail.com" <bsingharora@gmail.com>,
"kamezawa.hiroyu@jp.fujitsu.com" <kamezawa.hiroyu@jp.fujitsu.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"kosaki.motohiro@jp.fujitsu.com" <kosaki.motohiro@jp.fujitsu.com>,
Rik van Riel <riel@redhat.com>, "mel@csn.ul.ie" <mel@csn.ul.ie>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"cgroups@vger.kernel.org" <cgroups@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Ying Han <yinghan@google.com>
Subject: Re: [PATCH] memcg: implement low limits
Date: Thu, 28 Feb 2013 15:30:52 +0100 [thread overview]
Message-ID: <20130228143052.GE6573@dhcp22.suse.cz> (raw)
In-Reply-To: <38951361977052@webcorp2g.yandex-team.ru>
On Wed 27-02-13 18:57:32, Roman Gushchin wrote:
[...]
> >> + *
> >> + */
> >> +unsigned int mem_cgroup_low_limit_scale(struct lruvec *lruvec)
> >> +{
> >> + struct mem_cgroup_per_zone *mz;
> >> + struct mem_cgroup *memcg;
> >> + unsigned long long low_limit;
> >> + unsigned long long usage;
> >> + unsigned int i;
> >> +
> >> + mz = container_of(lruvec, struct mem_cgroup_per_zone, lruvec);
> >> + memcg = mz->memcg;
> >> + if (!memcg)
> >> + return 0;
> >> +
> >> + low_limit = res_counter_read_u64(&memcg->res, RES_LOW_LIMIT);
> >> + if (!low_limit)
> >> + return 0;
> >> +
> >> + usage = res_counter_read_u64(&memcg->res, RES_USAGE);
> >> +
> >> + if (usage < low_limit)
> >> + return DEF_PRIORITY - 2;
> >> +
> >> + for (i = 0; i < DEF_PRIORITY - 2; i++)
> >> + if (usage - low_limit > (usage >> (i + 3)))
> >> + break;
> >
> > why this doesn't depend in the current reclaim priority?
>
> How do you want to use reclaim priority here?
But then you can get up to 2*DEF_PRIORITY-2 priority (in
get_scan_count) in the end and we are back to my original and more
fundamental objection that the low_limit depends on the group size
because small groups basically do not get scanned when under/close_to
limit while big groups do get scanned and reclaimed.
> I don't like an idea to start ignoring low limit on some priorities.
Well, but you are doing that already. If you are reclaiming for prio 0 then
you add up just DEF_PRIORITY-2 which means you reclaim for all groups with
more than 1024 pages on the LRUs.
[...]
--
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:[~2013-02-28 14:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 8:02 Roman Gushchin
2013-02-27 8:20 ` Greg Thelen
2013-02-27 10:11 ` Roman Gushchin
2013-02-27 9:40 ` Michal Hocko
2013-02-27 10:39 ` Roman Gushchin
2013-02-27 16:13 ` Michal Hocko
2013-02-28 11:13 ` Roman Gushchin
2013-02-28 13:02 ` Michal Hocko
2013-02-27 14:57 ` Roman Gushchin
2013-02-28 14:30 ` 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=20130228143052.GE6573@dhcp22.suse.cz \
--to=mhocko@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=bsingharora@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=klamm@yandex-team.ru \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=riel@redhat.com \
--cc=yinghan@google.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