From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: "linux-mm@kvack.org" <linux-mm@kvack.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
"menage@google.com" <menage@google.com>,
"balbir@linux.vnet.ibm.com" <balbir@linux.vnet.ibm.com>,
"xemul@openvz.org" <xemul@openvz.org>,
"yamamoto@valinux.co.jp" <yamamoto@valinux.co.jp>,
"nishimura@mxp.nes.nec.co.jp" <nishimura@mxp.nes.nec.co.jp>,
"lizf@cn.fujitsu.com" <lizf@cn.fujitsu.com>
Subject: [PATCH 0/6] memcg: hierarchy updates (v4)
Date: Fri, 13 Jun 2008 18:27:14 +0900 [thread overview]
Message-ID: <20080613182714.265fe6d2.kamezawa.hiroyu@jp.fujitsu.com> (raw)
Hi, this is memcg hierarchy series v4. but I changed the title.
Thank you for many replies to v3.
This is against 2.6.26-rc5-mm3.
I rearranged the patch stack and much amount of codes are rewritten.
I think I answers most of advices in this version. If I misses, please
point out again, sorry.
Balbir, I'd like to write a generic infrastructure to allow me and you to
implement what we want. So, please check patches in the view,
how res_counter is used and whether my codes can have a bad effect to
what you want or not.
Changelog:
- rearranged patch stack.
- "limit change" handling is divided.
- moves basic res_counter handling to res_counter from memcg.
Short description of patches.
- [1/6] ...a callback for change-of-limit support to res_counter.
- [2/6] ...make use of change-of-limit support in memcg.
- [3/6] ...a special case of implicit change-of-limit at rmdir()
- [4/6] ...a hierarchy support infrastructure for res_counter.
- [5/6] ...HARDWALL hierarchy support in res_counter.
- [6/6] ...HARDWALL hierarhcy in memcg.
It seems rc5-mm3 needs more test and I will not be able to answer e-mail quickly.
please check when you have free time ;)
Anyway, I'd like to push [1/6] and [2/6] , at first. Others will be scheduled
later.
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:[~2008-06-13 9:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 9:27 KAMEZAWA Hiroyuki [this message]
2008-06-13 9:29 ` [PATCH 1/6] res_counter: handle limit change KAMEZAWA Hiroyuki
2008-06-16 6:38 ` Pavel Emelyanov
2008-06-16 7:39 ` kamezawa.hiroyu
2008-06-16 7:51 ` Pavel Emelyanov
2008-06-16 8:17 ` kamezawa.hiroyu
2008-06-16 8:23 ` Pavel Emelyanov
2008-06-16 8:32 ` kamezawa.hiroyu
2008-06-16 8:47 ` Pavel Emelyanov
2008-06-16 9:01 ` kamezawa.hiroyu
2008-06-16 8:53 ` kamezawa.hiroyu
2008-06-16 9:00 ` Pavel Emelyanov
2008-06-16 8:57 ` Balbir Singh
2008-06-16 8:59 ` Pavel Emelyanov
2008-06-16 9:04 ` kamezawa.hiroyu
2008-06-16 12:29 ` Balbir Singh
2008-06-16 13:26 ` kamezawa.hiroyu
2008-06-20 5:09 ` Paul Menage
2008-06-23 22:40 ` Randy Dunlap
2008-06-13 9:30 ` [PATCH 2/6] memcg: " KAMEZAWA Hiroyuki
2008-06-13 9:31 ` [PATCH 3/6] memcg: reset limit at rmdir KAMEZAWA Hiroyuki
2008-06-13 9:34 ` [PATCH 4/6] res_counter: basic hierarchy support KAMEZAWA Hiroyuki
2008-06-23 22:37 ` Randy Dunlap
2008-06-13 9:36 ` [PATCH 5/6] res_counter: HARDWALL hierarchy KAMEZAWA Hiroyuki
2008-06-13 9:37 ` [PATCH 6/6] memcg: " KAMEZAWA Hiroyuki
2008-06-23 22:29 ` Randy Dunlap
2008-06-24 3:37 ` 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=20080613182714.265fe6d2.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.com \
--cc=nishimura@mxp.nes.nec.co.jp \
--cc=xemul@openvz.org \
--cc=yamamoto@valinux.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