From: Michal Hocko <mhocko@suse.cz>
To: Hillf Danton <dhillf@gmail.com>
Cc: linux-mm@kvack.org, Johannes Weiner <hannes@cmpxchg.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Hugh Dickins <hughd@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Balbir Singh <bsingharora@gmail.com>
Subject: Re: [PATCH] mm: memcg: remove checking reclaim order in soft limit reclaim
Date: Wed, 18 Jan 2012 14:40:53 +0100 [thread overview]
Message-ID: <20120118134053.GD31112@tiehlicka.suse.cz> (raw)
In-Reply-To: <CAJd=RBAyqPwKERQL4JyCO38gjE=y8_qasHTbLtMGWqtZ1JFnUg@mail.gmail.com>
On Wed 18-01-12 20:30:41, Hillf Danton wrote:
> On Tue, Jan 17, 2012 at 10:07 PM, Michal Hocko <mhocko@suse.cz> wrote:
> > On Tue 17-01-12 21:29:52, Hillf Danton wrote:
> >> On Tue, Jan 17, 2012 at 9:16 PM, Michal Hocko <mhocko@suse.cz> wrote:
> >> > Hi,
> >> >
> >> > On Tue 17-01-12 20:47:59, Hillf Danton wrote:
> >> >> If async order-O reclaim expected here, it is settled down when setting up scan
> >> >> control, with scan priority hacked to be zero. Other than that, deny of reclaim
> >> >> should be removed.
> >> >
> >> > Maybe I have misunderstood you but this is not right. The check is to
> >> > protect from the _global_ reclaim with order > 0 when we prevent from
> >> > memcg soft reclaim.
> >> >
> >> need to bear mm hog in this way?
> >
> > Could you be more specific? Are you trying to fix any particular
> > problem?
> >
> My thought is simple, the outcome of softlimit reclaim depends little on the
> value of reclaim order, zero or not, and only exceeding is reclaimed, so
> selective response to swapd's request is incorrect.
OK, got your point, finally. Let's add Balbir (the proposed patch can
be found at https://lkml.org/lkml/2012/1/17/166) to the CC list because
this seems to be a design decision.
I always thought that this is because we want non-userspace (high order)
mem pressure to be handled by the global reclaim only. And it makes some
sense to me because it is little bit strange to reclaim for order-0
while the request is for an higher order. I guess this might lead to an
extensive and pointless reclaiming because we might end up with many
free pages which cannot satisfy higher order allocation.
On the other hand, it is true that the documentation says that the soft
limit is considered when "the system detects memory contention or low
memory" which doesn't say that the contention comes from memcg accounted
memory.
Anyway this changes the current behavior so it would better come with
much better justification which shows that over reclaim doesn't happen
and that we will not see higher latencies with higher order allocations.
Thanks
--
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-01-18 13:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 12:47 [PATCH] mm: memcg: remove checking reclaim order in soft limit reclaim Hillf Danton
2012-01-17 13:16 ` Michal Hocko
2012-01-17 13:29 ` Hillf Danton
2012-01-17 14:07 ` Michal Hocko
2012-01-18 12:30 ` Hillf Danton
2012-01-18 13:40 ` Michal Hocko [this message]
2012-01-18 14:01 ` Hillf Danton
2012-01-18 15:13 ` Michal Hocko
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=20120118134053.GD31112@tiehlicka.suse.cz \
--to=mhocko@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=bsingharora@gmail.com \
--cc=dhillf@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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).