From: Michal Hocko <mhocko@suse.cz>
To: linux-mm@kvack.org, cgroups@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Balbir Singh <bsingharora@gmail.com>,
Hugh Dickins <hughd@google.com>, Ying Han <yinghan@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
Konstantin Khlebnikov <khlebnikov@openvz.org>,
Glauber Costa <glommer@parallels.com>
Subject: Re: memcg-devel updated for v3.3
Date: Thu, 22 Mar 2012 10:11:47 +0100 [thread overview]
Message-ID: <20120322091147.GB18665@tiehlicka.suse.cz> (raw)
In-Reply-To: <20120321094545.GA10450@tiehlicka.suse.cz>
On Wed 21-03-12 10:45:45, Michal Hocko wrote:
[...]
> Hugh Dickins (15):
> memcg-clear-pc-mem_cgorup-if-necessary-fix-2
> memcg-clear-pc-mem_cgorup-if-necessary fix 3
> memcg: fix page migration to reset_owner
> memcg: replace MEM_CONT by MEM_RES_CTLR
> memcg: replace mem and mem_cont stragglers
> memcg: lru_size instead of MEM_CGROUP_ZSTAT
> memcg: enum lru_list lru
> memcg: remove redundant returns
> idr: make idr_get_next() good for rcu_read_lock()
> cgroup: revert ss_id_lock to spinlock
> memcg: let css_get_next() rely upon rcu_read_lock()
> memcg: remove PCG_CACHE page_cgroup flag fix
> memcg: remove PCG_CACHE page_cgroup flag fix2
> memcg: remove PCG_FILE_MAPPED fix cosmetic fix
> memcg: fix GPF when cgroup removal races with last exit
I have just noticed I forgot about one fix.
Hugh Dickins (1):
memcg: fix deadlock by avoiding stat lock when anon
pushed and sorry
--
Michal Hocko
SUSE Labs
SUSE LINUX s.r.o.
Lihovarska 1060/12
190 00 Praha 9
Czech Republic
prev parent reply other threads:[~2012-03-22 9:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 9:45 Michal Hocko
2012-03-22 9:11 ` Michal Hocko [this message]
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=20120322091147.GB18665@tiehlicka.suse.cz \
--to=mhocko@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=bsingharora@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=glommer@parallels.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=khlebnikov@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=yinghan@google.com \
/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
all inboxes | Powered by JetHome®