From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: "linux-mm@kvack.org" <linux-mm@kvack.org>
Cc: "nishimura@mxp.nes.nec.co.jp" <nishimura@mxp.nes.nec.co.jp>,
"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>
Subject: [PATCH 0/5] memcg: towards I/O aware memcg v7.
Date: Wed, 1 Sep 2010 15:39:51 +0900 [thread overview]
Message-ID: <20100901153951.bc82c021.kamezawa.hiroyu@jp.fujitsu.com> (raw)
Major changes from v6 is
a) added documentation about CSS ID.
b) fixed typos and bugs.
c) refleshed some comments
based on mmotm-2010-08-27
Patch brief view:
1. changes css ID allocation in kernel/cgroup.c
2. use ID-array in memcg.
3. record ID to page_cgroup rather than pointer.
4. make update_file_mapped to be RCU aware routine instead of spinlock.
5. make update_file_mapped as general-purpose function.
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 reply other threads:[~2010-09-01 6:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 6:39 KAMEZAWA Hiroyuki [this message]
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
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=20100901153951.bc82c021.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=gthelen@google.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 \
--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