From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
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>,
Pavel Emelyanov <xemul@openvz.org>,
Dan Malek <dan@embeddedalley.com>,
Vladislav Buzov <vbuzov@embeddedalley.com>,
Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>,
Alexander Shishkin <virtuoso@slind.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/4] cgroup notifications API and memory thresholds
Date: Sat, 26 Dec 2009 19:00:11 +0530 [thread overview]
Message-ID: <20091226133011.GA10944@balbir.in.ibm.com> (raw)
In-Reply-To: <cover.1261786326.git.kirill@shutemov.name>
* Kirill A. Shutemov <kirill@shutemov.name> [2009-12-26 02:30:56]:
> This patchset introduces eventfd-based API for notifications in cgroups and
> implements memory notifications on top of it.
>
> It uses statistics in memory controler to track memory usage.
>
> Output of time(1) on building kernel on tmpfs:
>
> Root cgroup before changes:
> make -j2 506.37 user 60.93s system 193% cpu 4:52.77 total
> Non-root cgroup before changes:
> make -j2 507.14 user 62.66s system 193% cpu 4:54.74 total
> Root cgroup after changes (0 thresholds):
> make -j2 507.13 user 62.20s system 193% cpu 4:53.55 total
> Non-root cgroup after changes (0 thresholds):
> make -j2 507.70 user 64.20s system 193% cpu 4:55.70 total
> Root cgroup after changes (1 thresholds, never crossed):
> make -j2 506.97 user 62.20s system 193% cpu 4:53.90 total
> Non-root cgroup after changes (1 thresholds, never crossed):
> make -j2 507.55 user 64.08s system 193% cpu 4:55.63 total
>
> Any comments?
Could you please add some documentation for end users. I've just
compiled a kernel with your changes for test. Also, is there a reason
not to use cgroupstats?
--
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-12-26 13:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-26 0:30 Kirill A. Shutemov
2009-12-26 0:30 ` [PATCH v3 1/4] cgroup: implement eventfd-based generic API for notifications Kirill A. Shutemov
2009-12-26 0:30 ` [PATCH v3 2/4] memcg: extract mem_group_usage() from mem_cgroup_read() Kirill A. Shutemov
2009-12-26 0:30 ` [PATCH v3 3/4] memcg: rework usage of stats by soft limit Kirill A. Shutemov
2009-12-26 0:31 ` [PATCH v3 4/4] memcg: implement memory thresholds Kirill A. Shutemov
2009-12-26 13:30 ` Balbir Singh [this message]
2009-12-26 23:37 ` [PATCH v3 0/4] cgroup notifications API and " 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=20091226133011.GA10944@balbir.in.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.linux-foundation.org \
--cc=dan@embeddedalley.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kirill@shutemov.name \
--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=virtuoso@slind.org \
--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