From: Andrew Morton <akpm@linux-foundation.org>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: a.p.zijlstra@chello.nl, balbir@linux.vnet.ibm.com, dev@sw.ru,
ebiederm@xmission.com, herbert@13thfloor.at, menage@google.com,
nickpiggin@yahoo.com.au, rientjes@google.com,
svaidy@linux.vnet.ibm.com, xemul@openvz.org,
mm-commits@vger.kernel.org
Subject: Re: - memory-cgroup-enhancements-add-pre_destroy-handler.patch removed from -mm tree
Date: Mon, 5 Nov 2007 23:50:15 -0800 [thread overview]
Message-ID: <20071105235015.eb968ad7.akpm@linux-foundation.org> (raw)
In-Reply-To: <20071106164447.98fa9032.kamezawa.hiroyu@jp.fujitsu.com>
On Tue, 6 Nov 2007 16:44:47 +0900 KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> On Mon, 05 Nov 2007 23:14:40 -0800
> akpm@linux-foundation.org wrote:
>
> >
> > The patch titled
> > memory cgroup enhancements: add pre_destroy handler
> > has been removed from the -mm tree. Its filename was
> > memory-cgroup-enhancements-add-pre_destroy-handler.patch
> >
> > This patch was dropped because I can't get it to compile - new version after next -mm, please
> >
>
> Hmm, ok. I'll reschedule this and next one.
Thanks.
> But is there objections to pre_destroy handler ?
Dunno, I haven't been paying much attention. Has anyone else? It's a bit
suspicious that nobody noticed that this would cause obvious build
errors.
More reviewing effort please, guys.
> If we should deal with reference count of following in another way,
> ==
> page->page_cgroup->memory_cgroup, memory_cgroup contains css.
> page_cgroup has ref to css.
> ==
> I'll consider something. (for example, add refcnt to memory_cgroup itself.)
>
> Changing above may allow us to guarantee that if no task, css's refcnt is 0.
next prev parent reply other threads:[~2007-11-06 7:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 7:14 - memory-cgroup-enhancements-add-pre_destroy-handler.patch removed from -mm tree akpm
[not found] ` <20071106164447.98fa9032.kamezawa.hiroyu@jp.fujitsu.com>
2007-11-06 7:50 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-08 8:04 akpm
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=20071105235015.eb968ad7.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=a.p.zijlstra@chello.nl \
--cc=balbir@linux.vnet.ibm.com \
--cc=dev@sw.ru \
--cc=ebiederm@xmission.com \
--cc=herbert@13thfloor.at \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=mm-commits@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=rientjes@google.com \
--cc=svaidy@linux.vnet.ibm.com \
--cc=xemul@openvz.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.