From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
Cc: 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:06:13 +0900 [thread overview]
Message-ID: <20090326150613.09aacf0d.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20090326145148.ba722e1e.nishimura@mxp.nes.nec.co.jp>
On Thu, 26 Mar 2009 14:51:48 +0900
Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp> wrote:
> > Ah, i see. good cacth.
> > But it seems to be the patch is a bit big and includes duplications.
> > Can't we divide this patch into 2 and reduce modification ?
> >
> Will do if needed.
> (returning mem_over_limit part and implementing
> add_to_page_cache_store_memcg part, perhaps)
>
> > mem_cgroup_shrink_usage() should do something proper...
> > My brief thinking is a patch like this, how do you think ?
> >
> I thought the same direction at first.
> But it's similar to the old implementation before c9b0ed51 conceptually,
> so I chose a new direction.
>
> I withdraw my patch if you prefer this direction :)
>
Ah, my basic plan is.
- BUGFIX should be simple.
- If clean up is necessary, it should be on other patch.
I have no objections to make memcg cleaner.
> > Maybe renaming this function is appropriate...
> I think so too if we go in this direction.
>
> Just a few comments below.
>
Thanks,
> > ==
> > mem_cgroup_shrink_usage() is called by shmem, but its purpose is
> > not different from try_charge().
> >
> > In current behavior, it ignores upward hierarchy and doesn't update
> > OOM status of memcg. That's bad. We can simply call try_charge()
> > and drop charge later.
> >
> > Reported-by: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
> > Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> > ---
> > mm/memcontrol.c | 16 ++++++++--------
> > 1 file changed, 8 insertions(+), 8 deletions(-)
> >
> > Index: test/mm/memcontrol.c
> > ===================================================================
> > --- test.orig/mm/memcontrol.c
> > +++ test/mm/memcontrol.c
> > @@ -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.
Thanks,
-Kame
--
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:19 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 [this message]
2009-03-26 6:17 ` Daisuke Nishimura
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=20090326150613.09aacf0d.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=balbir@in.ibm.com \
--cc=hugh@veritas.com \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=nishimura@mxp.nes.nec.co.jp \
/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