From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
"nishimura@mxp.nes.nec.co.jp" <nishimura@mxp.nes.nec.co.jp>
Subject: memcg merge for 2.6.32 (was Re: 2.6.32 -mm merge plans)
Date: Wed, 16 Sep 2009 13:07:27 +0530 [thread overview]
Message-ID: <20090916073727.GP4846@balbir.in.ibm.com> (raw)
In-Reply-To: <20090915161535.db0a6904.akpm@linux-foundation.org>
* Andrew Morton <akpm@linux-foundation.org> [2009-09-15 16:15:35]:
>
> memcg-remove-the-overhead-associated-with-the-root-cgroup.patch
> memcg-remove-the-overhead-associated-with-the-root-cgroup-fix.patch
> memcg-remove-the-overhead-associated-with-the-root-cgroup-fix-2.patch
> #memcg-add-comments-explaining-memory-barriers.patch: needs update (Balbir)
> memcg-add-comments-explaining-memory-barriers.patch
> memcg-add-comments-explaining-memory-barriers-checkpatch-fixes.patch
> memory-controller-soft-limit-documentation-v9.patch
> memory-controller-soft-limit-interface-v9.patch
> memory-controller-soft-limit-organize-cgroups-v9.patch
> memory-controller-soft-limit-organize-cgroups-v9-fix.patch
> memory-controller-soft-limit-refactor-reclaim-flags-v9.patch
> memory-controller-soft-limit-reclaim-on-contention-v9.patch
> memory-controller-soft-limit-reclaim-on-contention-v9-fix.patch
> memory-controller-soft-limit-reclaim-on-contention-v9-fix-softlimit-css-refcnt-handling.patch
> memory-controller-soft-limit-reclaim-on-contention-v9-fix-softlimit-css-refcnt-handling-fix.patch
> memcg-improve-resource-counter-scalability.patch
> memcg-improve-resource-counter-scalability-checkpatch-fixes.patch
> memcg-improve-resource-counter-scalability-v5.patch
> memcg-show-swap-usage-in-stat-file.patch
> memcg-show-swap-usage-in-stat-file-fix.patch
>
> Merge after checking with Balbir
I think these are ready for merging, I'll let Kame and Daisuke comment
on it more. The resource counter scalability patch is the most
important patch in the series.
--
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-09-16 7:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 23:15 2.6.32 -mm merge plans Andrew Morton
2009-09-16 3:46 ` Dmitry Torokhov
2009-09-16 4:14 ` Andrew Morton
2009-09-16 8:33 ` David Härdeman
2009-09-16 15:00 ` Bjorn Helgaas
2009-09-16 20:00 ` Andrew Morton
2009-09-16 7:37 ` Balbir Singh [this message]
2009-09-16 7:51 ` memcg merge for 2.6.32 (was Re: 2.6.32 -mm merge plans) Daisuke Nishimura
2009-09-16 7:58 ` KAMEZAWA Hiroyuki
2009-09-16 8:45 ` stack limits [was Re: 2.6.32 -mm merge plans] Pavel Machek
2009-09-16 9:42 ` hwpoison fixes was Re: 2.6.32 -mm merge plans Andi Kleen
2009-09-17 20:15 ` cgrooups && " Oleg Nesterov
2009-09-17 20:38 ` Andrew Morton
2009-09-17 21:08 ` Oleg Nesterov
2009-09-17 20:32 ` do_wait() changes " Oleg Nesterov
2009-09-17 20:46 ` tracehooks " Oleg Nesterov
2009-09-17 21:56 ` Roland McGrath
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=20090916073727.GP4846@balbir.in.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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;
as well as URLs for NNTP newsgroup(s).