From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: nishimura@mxp.nes.nec.co.jp
Cc: containers@lists.linux-foundation.org, linux-mm@kvack.org,
Paul Menage <menage@google.com>, Li Zefan <lizf@cn.fujitsu.com>,
Andrew Morton <akpm@linux-foundation.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
Pavel Emelyanov <xemul@openvz.org>,
Dan Malek <dan@embeddedalley.com>,
Vladislav Buzov <vbuzov@embeddedalley.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC v2 4/4] memcg: implement memory thresholds
Date: Sat, 12 Dec 2009 15:13:52 +0200 [thread overview]
Message-ID: <cc557aab0912120513q6e9cd518y1af2c6fbbd407b85@mail.gmail.com> (raw)
In-Reply-To: <cc557aab0912120511r7c83e97di3f97d2bb5eae326c@mail.gmail.com>
On Sat, Dec 12, 2009 at 3:11 PM, Kirill A. Shutemov
<kirill@shutemov.name> wrote:
> Ok, I'll move it. It will affect performance of
> mem_cgroup_invalidate_thresholds(),
> but I don't think that it's important.
s/mem_cgroup_invalidate_thresholds()/mem_cgroup_register_event() and
mem_cgroup_unregister_event()/
--
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-12-12 13:13 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 22:59 [PATCH RFC v2 0/4] cgroup notifications API and " Kirill A. Shutemov
2009-12-11 22:59 ` [PATCH RFC v2 1/4] cgroup: implement eventfd-based generic API for notifications Kirill A. Shutemov
2009-12-11 22:59 ` [PATCH RFC v2 2/4] memcg: extract mem_group_usage() from mem_cgroup_read() Kirill A. Shutemov
2009-12-11 22:59 ` [PATCH RFC v2 3/4] memcg: rework usage of stats by soft limit Kirill A. Shutemov
2009-12-11 22:59 ` [PATCH RFC v2 4/4] memcg: implement memory thresholds Kirill A. Shutemov
2009-12-12 3:19 ` Daisuke Nishimura
2009-12-12 13:11 ` Kirill A. Shutemov
2009-12-12 13:13 ` Kirill A. Shutemov [this message]
2009-12-15 1:58 ` KAMEZAWA Hiroyuki
2009-12-15 10:46 ` Kirill A. Shutemov
2009-12-15 11:09 ` KAMEZAWA Hiroyuki
2009-12-12 3:50 ` [PATCH RFC v2 3/4] memcg: rework usage of stats by soft limit Daisuke Nishimura
2009-12-12 13:06 ` Kirill A. Shutemov
2009-12-12 14:34 ` Daisuke Nishimura
2009-12-12 19:46 ` Kirill A. Shutemov
2009-12-13 1:30 ` Daisuke Nishimura
2009-12-15 1:35 ` KAMEZAWA Hiroyuki
2009-12-15 7:48 ` Kirill A. Shutemov
2009-12-15 8:07 ` KAMEZAWA Hiroyuki
2009-12-16 8:40 ` [PATCH RFC v2 2/4] memcg: extract mem_group_usage() from mem_cgroup_read() Balbir Singh
2009-12-15 9:11 ` [PATCH RFC v2 1/4] cgroup: implement eventfd-based generic API for notifications Kirill A. Shutemov
2009-12-15 9:35 ` KAMEZAWA Hiroyuki
2009-12-15 10:30 ` Kirill A. Shutemov
2009-12-15 15:03 ` Kirill A. Shutemov
2009-12-15 23:55 ` KAMEZAWA Hiroyuki
2009-12-16 1:44 ` Li Zefan
2009-12-16 2:00 ` Li Zefan
2009-12-16 5:46 ` Kirill A. Shutemov
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=cc557aab0912120513q6e9cd518y1af2c6fbbd407b85@mail.gmail.com \
--to=kirill@shutemov.name \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=containers@lists.linux-foundation.org \
--cc=dan@embeddedalley.com \
--cc=kamezawa.hiroyu@jp.fujitsu.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 \
--cc=vbuzov@embeddedalley.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox