linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.cz>
To: Li Zefan <lizefan@huawei.com>
Cc: Tejun Heo <tj@kernel.org>, Johannes Weiner <hannes@cmpxchg.org>,
	LKML <linux-kernel@vger.kernel.org>,
	cgroups <cgroups@vger.kernel.org>,
	linux-mm@kvack.org,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	Glauber Costa <glommer@gmail.com>
Subject: Re: [PATCH v3 5/9] memcg: use css_get/put when charging/uncharging kmem
Date: Thu, 13 Jun 2013 17:54:53 +0200	[thread overview]
Message-ID: <20130613155453.GK23070@dhcp22.suse.cz> (raw)
In-Reply-To: <20130613155319.GJ23070@dhcp22.suse.cz>

[Fix Glauber's new address]

On Thu 13-06-13 17:53:19, Michal Hocko wrote:
> On Thu 13-06-13 17:12:55, Li Zefan wrote:
> > Sorry for updating the patchset so late.
> > 
> > I've made some changes for the memory barrier thing, and I agree with
> > Michal that there can be improvement but can be a separate patch.
> > 
> > If this version is ok for everyone, I'll send the whole patchset out
> > to Andrew.
> > 
> > =========================
> > 
> > Use css_get/put instead of mem_cgroup_get/put.
> > 
> > We can't do a simple replacement, because here mem_cgroup_put()
> > is called during mem_cgroup_css_free(), while mem_cgroup_css_free()
> > won't be called until css refcnt goes down to 0.
> > 
> > Instead we increment css refcnt in mem_cgroup_css_offline(), and
> > then check if there's still kmem charges. If not, css refcnt will
> > be decremented immediately, 
> 
> > otherwise the refcnt won't be decremented when kmem charges goes down
> > to 0.
> 
> This is a bit confusing. What about "otherwise the css refcount will be
> released after the last kmem allocation is uncharged."
> 
> > 
> > v3:
> > - changed wmb() to smp_smb(), and moved it to memcg_kmem_mark_dead(),
> >   and added comment.
> > 
> > v2:
> > - added wmb() in kmem_cgroup_css_offline(), pointed out by Michal
> > - revised comments as suggested by Michal
> > - fixed to check if kmem is activated in kmem_cgroup_css_offline()
> > 
> > Signed-off-by: Li Zefan <lizefan@huawei.com>
> > Acked-by: Michal Hocko <mhocko@suse.cz>
> > Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> > ---
> >  mm/memcontrol.c | 70 ++++++++++++++++++++++++++++++++++++---------------------
> >  1 file changed, 45 insertions(+), 25 deletions(-)
> > 
> > diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> > index 466c595..76dcd0e 100644
> > --- a/mm/memcontrol.c
> > +++ b/mm/memcontrol.c
> > @@ -416,6 +416,11 @@ static void memcg_kmem_clear_activated(struct mem_cgroup *memcg)
> >  
> >  static void memcg_kmem_mark_dead(struct mem_cgroup *memcg)
> >  {
> > +	/*
> > +	 * We need to call css_get() first, because memcg_uncharge_kmem()
> > +	 * will call css_put() if it sees the memcg is dead.
> > +	 */
> > +	smb_wmb();
> >  	if (test_bit(KMEM_ACCOUNTED_ACTIVE, &memcg->kmem_account_flags))
> >  		set_bit(KMEM_ACCOUNTED_DEAD, &memcg->kmem_account_flags);
> 
> I do not feel strongly about that but maybe open coding this in
> mem_cgroup_css_offline would be even better. There is only single caller
> and there is smaller chance somebody will use the function incorrectly
> later on.
> 
> So I leave the decision on you because this doesn't matter much.
> 
> [...]
> -- 
> Michal Hocko
> SUSE Labs
> --
> To unsubscribe from this list: send the line "unsubscribe cgroups" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

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

  reply	other threads:[~2013-06-13 15:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-13  9:12 Li Zefan
2013-06-13 15:53 ` Michal Hocko
2013-06-13 15:54   ` Michal Hocko [this message]
2013-06-14  1:17   ` Li Zefan
2013-06-14 10:56     ` Glauber Costa
2013-06-13 19:53 ` Tejun Heo

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=20130613155453.GK23070@dhcp22.suse.cz \
    --to=mhocko@suse.cz \
    --cc=cgroups@vger.kernel.org \
    --cc=glommer@gmail.com \
    --cc=hannes@cmpxchg.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lizefan@huawei.com \
    --cc=tj@kernel.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