linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.cz>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	torvalds@linux-foundation.org, nishimura@mxp.nes.nec.co.jp,
	yinghan@google.com, linux-mm@kvack.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [patch 14/22] memcg: fix direct softlimit reclaim to be called in limit path
Date: Tue, 28 Jun 2011 10:53:36 +0200	[thread overview]
Message-ID: <20110628085335.GA17961@tiehlicka.suse.cz> (raw)
In-Reply-To: <20110628170649.87043e05.kamezawa.hiroyu@jp.fujitsu.com>

On Tue 28-06-11 17:06:49, KAMEZAWA Hiroyuki wrote:
> On Tue, 28 Jun 2011 10:08:47 +0200
> Michal Hocko <mhocko@suse.cz> wrote:
> 
> > I am sorry, that I am answering that late but I didn't get to this
> > sooner.
> > 
> > On Mon 27-06-11 16:18:12, Andrew Morton wrote:
> > > From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> > > 
> > > commit d149e3b ("memcg: add the soft_limit reclaim in global direct
> > > reclaim") adds a softlimit hook to shrink_zones().  By this, soft limit is
> > > called as
> > > 
> > >    try_to_free_pages()
> > >        do_try_to_free_pages()
> > >            shrink_zones()
> > >                mem_cgroup_soft_limit_reclaim()
> > > 
> > > Then, direct reclaim is memcg softlimit hint aware, now.
> > > 
> > > But, the memory cgroup's "limit" path can call softlimit shrinker.
> > > 
> > >    try_to_free_mem_cgroup_pages()
> > >        do_try_to_free_pages()
> > >            shrink_zones()
> > >                mem_cgroup_soft_limit_reclaim()
> > > 
> > > This will cause a global reclaim when a memcg hits limit.
> > 
> > Sorry, I do not get it. How does it cause the global reclaim? Did you
> > mean soft reclaim?
> > 
> 
> yes. soft reclaim does global reclaim (in some means). 

But calling it global reclaim is rather confusing because in both paths
we have sc.mem_cgroup set to non-NULL which is evaluated as
!scanning_global_lru(sc). Anyway, this is not that important, I just
wanted to be sure what you meant by that comment.

-- 
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>

      reply	other threads:[~2011-06-28  8:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201106272318.p5RNICJW001465@imap1.linux-foundation.org>
2011-06-28  8:08 ` [patch 14/22] memcg: fix direct softlimit reclaim to be called in limit path Michal Hocko
2011-06-28  8:06   ` KAMEZAWA Hiroyuki
2011-06-28  8:53     ` 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=20110628085335.GA17961@tiehlicka.suse.cz \
    --to=mhocko@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nishimura@mxp.nes.nec.co.jp \
    --cc=torvalds@linux-foundation.org \
    --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;
as well as URLs for NNTP newsgroup(s).