From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
"nishimura@mxp.nes.nec.co.jp" <nishimura@mxp.nes.nec.co.jp>,
"lizf@cn.fujitsu.com" <lizf@cn.fujitsu.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Subject: Re: [RFC] Low overhead patches for the memory resource controller
Date: Thu, 14 May 2009 08:09:30 +0530 [thread overview]
Message-ID: <20090514023930.GT13394@balbir.in.ibm.com> (raw)
In-Reply-To: <20090514092405.1c3e6134.kamezawa.hiroyu@jp.fujitsu.com>
* KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> [2009-05-14 09:24:05]:
> On Thu, 14 May 2009 09:08:02 +0900
> KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
>
> > On Wed, 13 May 2009 21:02:18 +0530
> > Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
> >
> > > Important: Not for inclusion, for discussion only
> > >
> > > I've been experimenting with a version of the patches below. They add
> > > a PCGF_ROOT flag for tracking pages belonging to the root cgroup and
> > > disable LRU manipulation for them
> > >
> > > Caveats:
> > >
> > > 1. I've not checked accounting, accounting might be broken
> > > 2. I've not made the root cgroup as non limitable, we need to disable
> > > hard limits once we agree to go with this
> > >
> > >
> > > Tests
> > >
> > > Quick tests show an improvement with AIM9
> > >
> > > mmotm+patch mmtom-08-may-2009
> > > AIM9 1338.57 1338.17
> > > Dbase 18034.16 16021.58
> > > New Dbase 18482.24 16518.54
> > > Shared 9935.98 8882.11
> > > Compute 16619.81 15226.13
> > >
> > > Comments on the approach much appreciated
> > >
> > > Feature: Remove the overhead associated with the root cgroup
> > >
> > > From: Balbir Singh <balbir@linux.vnet.ibm.com>
> > >
> > > This patch changes the memory cgroup and removes the overhead associated
> > > with accounting all pages in the root cgroup. As a side-effect, we can
> > > no longer set a memory hard limit in the root cgroup.
> > >
> > > A new flag is used to track page_cgroup associated with the root cgroup
> > > pages.
> >
> > Hmm ? How about ignoring memcg completely when the thread belongs to ROOT
> > cgroup rather than this halfway method ?
> >
> BTW, this will make softlimit much harder. Do you have any idea on softlimit after
> this patch ?
>
Why would this make soft limit much harder? Since we charge up
hierarchially even now we ignore a cgroup if its soft limit is not
set. I am not sure I understand why.
--
Balbir
--
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-05-14 2:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 15:32 Balbir Singh
2009-05-14 0:08 ` KAMEZAWA Hiroyuki
2009-05-14 0:24 ` KAMEZAWA Hiroyuki
2009-05-14 2:39 ` Balbir Singh [this message]
2009-05-14 3:00 ` KAMEZAWA Hiroyuki
2009-05-14 2:56 ` Balbir Singh
2009-05-14 2:57 ` Balbir Singh
2009-05-14 0:42 ` KAMEZAWA Hiroyuki
2009-05-14 2:42 ` Balbir Singh
2009-05-14 1:35 ` KOSAKI Motohiro
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=20090514023930.GT13394@balbir.in.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.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