From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: "linux-mm@kvack.org" <linux-mm@kvack.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"menage@google.com" <menage@google.com>,
"lizf@cn.fujitsu.com" <lizf@cn.fujitsu.com>,
"balbir@linux.vnet.ibm.com" <balbir@linux.vnet.ibm.com>,
"nishimura@mxp.nes.nec.co.jp" <nishimura@mxp.nes.nec.co.jp>
Subject: [PATCH 0/6] memcg/cgroup, updates related to CSS ID
Date: Tue, 3 Feb 2009 18:03:20 +0900 [thread overview]
Message-ID: <20090203180320.9f29aa76.kamezawa.hiroyu@jp.fujitsu.com> (raw)
This is CSS ID series of patches. Some are for cgroup, others are for memcg.
No big changes from previous version. (*) is a patch for cgroup.
I think almost all comments are satisfied.
Isn't it not so bad time to start to test something new ?
[1/6] CSS ID for cgroup (*)
[2/6] use CSS ID in memcg's hierarchy.
[3/6] hierarchical stat for memcg
[4/6] fix shrink memory retry or -EBUSY
[5/6] fix oom killer under memcg hierarchy.
[6/6] fix frequent -EBUSY (*)
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:[~2009-02-03 9:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 9:03 KAMEZAWA Hiroyuki [this message]
2009-02-03 9:04 ` [PATCH 1/6] cgroup: CSS ID support KAMEZAWA Hiroyuki
2009-02-03 9:05 ` [PATCH 2/6] memcg: use CSS ID KAMEZAWA Hiroyuki
2009-02-03 9:05 ` [PATCH 3/6] memcg: hierarchical stat KAMEZAWA Hiroyuki
2009-02-03 9:07 ` [PATCH 4/6] memcg: fix shrinking memory to return -EBUSY by fixing retry algorithm KAMEZAWA Hiroyuki
2009-02-03 9:07 ` [PATCH 5/6] memcg: fix OOM killer under memcg KAMEZAWA Hiroyuki
2009-02-03 9:08 ` [PATCH 6/6] cgroup: fix frequent -EBUSY at rmdir 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=20090203180320.9f29aa76.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--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 \
/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