From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
Cc: Balbir Singh <balbir@linux.vnet.ibm.com>,
linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Li Zefan <lizf@cn.fujitsu.com>, Paul Menage <menage@google.com>
Subject: Re: [PATCH -mmotm 4/5] memcg: avoid oom during recharge at task move
Date: Thu, 3 Dec 2009 16:40:50 +0900 [thread overview]
Message-ID: <20091203164050.cc9678b1.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20091203150033.18dd293f.nishimura@mxp.nes.nec.co.jp>
On Thu, 3 Dec 2009 15:00:33 +0900
Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp> wrote:
> On Thu, 3 Dec 2009 14:22:43 +0900, KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> > On Thu, 3 Dec 2009 13:58:05 +0900
> > Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp> wrote:
> > > I'm now trying to decrease these overhead as much as possible, and the current
> > > status is bellow.
> > >
> > thanks.
> >
> > > (support for moving swap charge has not been pushed yet in my tree, so I tested
> > > only (1) and (2) cases.)
> > >
> > > | 252M | 512M | 1G
> > > -----+--------+--------+--------
> > > (1) | 0.20 | 0.40 | 0.81
> > > -----+--------+--------+--------
> > > (2) | 0.20 | 0.40 | 0.81
> > >
> > What is the unit of each numbers ? seconds ? And migration of a process with 1G bytes
> > requires 0.8sec ? But, hmm, speed up twice! sounds nice.
> >
> Ah, these numbers mean "seconds".
> I agree they are big yet...
>
But maybe reducing this will requires big efforts (or impossible).
So, this number is not very bad I think.
> >
> > > What I've done are are:
> > > - Instead of calling res_counter_uncharge() against the old cgroup in __mem_cgroup_move_account()
> > > evrytime, call res_counter_uncharge(PAGE_SIZE * moved) at the end of task migration once.
> > sounds reasonable.
> >
> > > - Instead of calling try_charge repeatedly, call res_counter_charge(PAGE_SIZE * necessary)
> > > in can_attach() if possible.
> > sounds reasonable, too.
> >
> > > - Not only res_counter_charge/uncharge, consolidate css_get()/put() too.
> > >
> > please do. But, hmm, I'd like to remove css_put/get per pages ;) But I put it aside now.
> >
> I do agree with you, but removing them would be a big change..
> This change reduced about 0.2sec in 1GB case, so it's a workaround for now.
>
please go ahead with coalesced css_put()/get().
I agree that workaround is necessary now.
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-12-03 7:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 4:27 [PATCH -mmotm 0/5] memcg: recharge at task move (19/Nov) Daisuke Nishimura
2009-11-19 4:28 ` [PATCH -mmotm 1/5] cgroup: introduce cancel_attach() Daisuke Nishimura
2009-11-19 21:42 ` Paul Menage
2009-11-19 23:49 ` Daisuke Nishimura
2009-11-19 4:29 ` [PATCH -mmotm 2/5] memcg: add interface to recharge at task move Daisuke Nishimura
2009-11-20 15:42 ` Balbir Singh
2009-11-23 23:56 ` Daisuke Nishimura
2009-11-19 4:29 ` [PATCH -mmotm 3/5] memcg: recharge charges of anonymous page Daisuke Nishimura
2009-11-19 4:30 ` [PATCH -mmotm 4/5] memcg: avoid oom during recharge at task move Daisuke Nishimura
2009-11-23 5:10 ` Balbir Singh
2009-11-24 2:43 ` Daisuke Nishimura
2009-11-27 4:58 ` Daisuke Nishimura
2009-12-03 4:58 ` Daisuke Nishimura
2009-12-03 5:22 ` KAMEZAWA Hiroyuki
2009-12-03 6:00 ` Daisuke Nishimura
2009-12-03 7:40 ` KAMEZAWA Hiroyuki [this message]
2009-11-19 4:31 ` [PATCH -mmotm 5/5] memcg: recharge charges of anonymous swap Daisuke Nishimura
2009-11-23 6:59 ` Balbir Singh
2009-11-24 7:54 ` Daisuke Nishimura
2009-11-19 19:03 ` [PATCH -mmotm 0/5] memcg: recharge at task move (19/Nov) Balbir Singh
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=20091203164050.cc9678b1.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.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