From: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: nishimura@mxp.nes.nec.co.jp, linux-mm <linux-mm@kvack.org>,
Balbir Singh <balbir@in.ibm.com>, Li Zefan <lizf@cn.fujitsu.com>,
Hugh Dickins <hugh@veritas.com>
Subject: Re: [RFC][BUGFIX][PATCH] memcg: fix shrink_usage
Date: Thu, 26 Mar 2009 15:17:33 +0900 [thread overview]
Message-ID: <20090326151733.1e36bf43.nishimura@mxp.nes.nec.co.jp> (raw)
In-Reply-To: <20090326150613.09aacf0d.kamezawa.hiroyu@jp.fujitsu.com>
> > > @@ -1655,16 +1655,16 @@ int mem_cgroup_shrink_usage(struct page
> > > if (unlikely(!mem))
> > > return 0;
> > >
> > > - do {
> > > - progress = mem_cgroup_hierarchical_reclaim(mem,
> > > - gfp_mask, true, false);
> > > - progress += mem_cgroup_check_under_limit(mem);
> > > - } while (!progress && --retry);
> > > + ret = __mem_cgroup_try_charge(NULL, GFP_KERNEL, mem, true);
> > >
> > I think we should simply call mem_cgroup_try_charge_swapin() w/o doing try_get.
> >
> Hmm, ok. Let me see again.
>
>
> > > + if (!ret) {
> > > + css_put(&mem->css); /* refcnt by charge *//
> > It should be done after res_counter_uncharge().
> >
> yes.
>
> > > + res_counter_uncharge(&mem->res, PAGE_SIZE);
> > > + if (do_swap_account)
> > > + res_counter_uncharge(&mem->memsw, PAGE_SIZE);
> > > + }
> > > css_put(&mem->css);
> > This put isn't needed if we don't try_get.
> >
> In shrink_usage() (not in this patch), we called try_get(), I think.
>
I meant that if we changed above part to try_charge_swapin w/o calling try_get
in shrink_usage, we don't need this put :)
And I think we can use cancel_charge_swapin at uncharge part.
So, mem_cgroup_shrink_usage would be like this ?
===
int mem_cgroup_shrink_usage(struct page *page,
struct mm_struct *mm,
gfp_t gfp_mask)
{
struct mem_cgroup *mem = NULL;
int ret;
ret = mem_cgroup_try_charge_swapin(mm, page, mask, &ptr);
if (!ret && ptr)
mem_cgroup_cancel_charge_swapin(ptr);
return ret;
}
===
Thanks,
Daisuke Nishimura.
--
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>
next prev parent reply other threads:[~2009-03-26 5:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 4:08 Daisuke Nishimura
2009-03-26 4:31 ` Daisuke Nishimura
2009-03-26 5:12 ` KAMEZAWA Hiroyuki
2009-03-26 5:51 ` Daisuke Nishimura
2009-03-26 6:06 ` KAMEZAWA Hiroyuki
2009-03-26 6:17 ` Daisuke Nishimura [this message]
2009-03-26 6:27 ` KAMEZAWA Hiroyuki
2009-03-26 6:38 ` Daisuke Nishimura
2009-03-26 6:50 ` KAMEZAWA Hiroyuki
2009-03-27 1:39 ` [BUGFIX][PATCH] " Daisuke Nishimura
2009-03-27 1:51 ` KAMEZAWA Hiroyuki
2009-03-26 6:00 ` [RFC][BUGFIX][PATCH] " Balbir Singh
2009-03-26 6:03 ` KAMEZAWA Hiroyuki
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=20090326151733.1e36bf43.nishimura@mxp.nes.nec.co.jp \
--to=nishimura@mxp.nes.nec.co.jp \
--cc=balbir@in.ibm.com \
--cc=hugh@veritas.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.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