Re: memcg merge for 2.6.32 (was Re: 2.6.32 -mm merge plans)

[Daisuke Nishimura]

On Wed, 16 Sep 2009 13:07:27 +0530, Balbir Singh <balbir@xxxxxxxxxxxxxxxxxx> wrote:
> * Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> [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.
> 
I don't have any objection for merging these patches.


Daisuke Nishimura.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/