From: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"balbir@linux.vnet.ibm.com" <balbir@linux.vnet.ibm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
gthelen@google.com, Munehiro Ikeda <m-ikeda@ds.jp.nec.com>,
menage@google.com, "lizf@cn.fujitsu.com" <lizf@cn.fujitsu.com>,
Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
Subject: Re: [PATCH 2/5] memcg: more use of css ID in memcg.
Date: Wed, 1 Sep 2010 16:52:38 +0900 [thread overview]
Message-ID: <20100901165238.5086e67d.nishimura@mxp.nes.nec.co.jp> (raw)
In-Reply-To: <20100901154259.5b17bb87.kamezawa.hiroyu@jp.fujitsu.com>
On Wed, 1 Sep 2010 15:42:59 +0900
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
>
> Now, memory cgroup has an ID per cgroup and make use of it at
> - hierarchy walk,
> - swap recording.
>
> This patch is for making more use of it. The final purpose is
> to replace page_cgroup->mem_cgroup's pointer to an unsigned short.
>
> This patch caches a pointer of memcg in an array. By this, we
> don't have to call css_lookup() which requires radix-hash walk.
> This saves some amount of memory footprint at lookup memcg via id.
>
> Changelog: 20100901
> - added unregster_memcg_id() and did some clean up.
> - removed ->valid.
> - fixed mem_cgroup_num counter handling.
>
> Changelog: 20100825
> - applied comments.
>
> Changelog: 20100811
> - adjusted onto mmotm-2010-08-11
> - fixed RCU related parts.
> - use attach_id() callback.
>
> Changelog: 20100804
> - fixed description in init/Kconfig
>
> Changelog: 20100730
> - fixed rcu_read_unlock() placement.
>
> Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Reviewed-by: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
--
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:[~2010-09-01 7:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 6:39 [PATCH 0/5] memcg: towards I/O aware memcg v7 KAMEZAWA Hiroyuki
2010-09-01 6:41 ` [PATCH 1/5] cgroup: change allocation of css ID placement KAMEZAWA Hiroyuki
2010-09-09 16:32 ` Greg Thelen
2010-09-09 23:46 ` KAMEZAWA Hiroyuki
2010-09-01 6:42 ` [PATCH 2/5] memcg: more use of css ID in memcg KAMEZAWA Hiroyuki
2010-09-01 7:52 ` Daisuke Nishimura [this message]
2010-09-01 6:43 ` [PATCH 3/5] memcg: use ID in page cgroup KAMEZAWA Hiroyuki
2010-09-01 6:45 ` [PATCH 4/5] memcg: light weight file mapped update lock system KAMEZAWA Hiroyuki
2010-09-01 6:45 ` [PATCH 5/5] memcg: generic file status accounting KAMEZAWA Hiroyuki
2010-09-09 4:44 ` [PATCH 0/5] memcg: towards I/O aware memcg v7 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=20100901165238.5086e67d.nishimura@mxp.nes.nec.co.jp \
--to=nishimura@mxp.nes.nec.co.jp \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=gthelen@google.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=m-ikeda@ds.jp.nec.com \
--cc=menage@google.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