From: Michal Hocko <mhocko@suse.cz>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Rik van Riel <riel@redhat.com>, Ying Han <yinghan@google.com>,
Mel Gorman <mel@csn.ul.ie>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Hillf Danton <dhillf@gmail.com>, Hugh Dickins <hughd@google.com>,
Dan Magenheimer <dan.magenheimer@oracle.com>,
linux-mm@kvack.org
Subject: Re: [PATCH V2 3/5] memcg: set soft_limit_in_bytes to 0 by default
Date: Mon, 16 Apr 2012 17:15:08 +0200 [thread overview]
Message-ID: <20120416151507.GC2014@tiehlicka.suse.cz> (raw)
In-Reply-To: <20120412022233.GF1787@cmpxchg.org>
On Thu 12-04-12 04:22:33, Johannes Weiner wrote:
> On Wed, Apr 11, 2012 at 08:45:33PM -0400, Rik van Riel wrote:
> > On 04/11/2012 06:00 PM, Ying Han wrote:
> > >1. If soft_limit are all set to MAX, it wastes first three periority iterations
> > >without scanning anything.
> > >
> > >2. By default every memcg is eligibal for softlimit reclaim, and we can also
> > >set the value to MAX for special memcg which is immune to soft limit reclaim.
> > >
> > >This idea is based on discussion with Michal and Johannes from LSF.
> >
> > Combined with patch 2/5, would this not result in always
> > returning "reclaim from this memcg" for groups without a
> > configured softlimit, while groups with a configured
> > softlimit only get reclaimed from when they are over
> > their limit?
> >
> > Is that the desired behaviour when a system has some
> > cgroups with a configured softlimit, and some without?
>
> Yes, in general I think this new behaviour is welcome.
>
> In the past, soft limits were only used to give excess memory a lower
> priority and there was no particular meaning associated with "being
> below your soft limit". This change makes it so that soft limits are
> actually a minimum guarantee, too, so you wouldn't get reclaimed if
> you behaved (if possible):
>
> A-unconfigured B-below-softlimit
> old: reclaim reclaim
> new: reclaim no reclaim (if possible)
>
> The much less obvious change here, however, is that we no longer put
> extra pressure on groups above their limit compared to unconfigured
> groups:
>
> A-unconfigured B-above-softlimit
> old: reclaim reclaim twice
> new: reclaim reclaim
Agreed and I guess that the above should be a part of the changelog.
This is changing previous behavior and we should rather be explicit
about that.
> I still think that it's a reasonable use case to put a soft limit on a
> workload to "nice" it memory-wise, without looking at the machine as a
> whole and configuring EVERY cgroup based on global knowledge and
> static partitioning of the machine.
--
Michal Hocko
SUSE Labs
SUSE LINUX s.r.o.
Lihovarska 1060/12
190 00 Praha 9
Czech Republic
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-04-16 15:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 22:00 Ying Han
2012-04-12 0:45 ` Rik van Riel
2012-04-12 2:22 ` Johannes Weiner
2012-04-16 15:15 ` Michal Hocko [this message]
2012-04-16 16:33 ` Ying Han
2012-04-12 3:46 ` Ying Han
2012-04-14 13:35 ` Hillf Danton
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=20120416151507.GC2014@tiehlicka.suse.cz \
--to=mhocko@suse.cz \
--cc=dan.magenheimer@oracle.com \
--cc=dhillf@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--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