From: "Aneesh Kumar K.V" <aneesh.kumar@linux•vnet.ibm.com>
To: David Rientjes <rientjes@google•com>,
Hiroyuki Kamezawa <kamezawa.hiroyuki@gmail•com>
Cc: Andrew Morton <akpm@linux-foundation•org>,
Randy Dunlap <rdunlap@xenotime•net>,
Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Richard Weinberger <richard@nod•at>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp•fujitsu.com>
Subject: Re: inux-next: Tree for Apr 27 (uml + mm/memcontrol.c)
Date: Fri, 04 May 2012 23:59:02 +0530 [thread overview]
Message-ID: <877gwryf4h.fsf@skywalker.in.ibm.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1205031454400.1631@chino.kir.corp.google.com>
David Rientjes <rientjes@google•com> writes:
>> Is this a claim that memory-intensive workloads will have the exact same
>> performance with and without memcg enabled?
> I've just run specjbb2005 three times on my system both with and without
> cgroup_disable=memory on the command line and it is consistently 1% faster
> without memcg. If I add XX:+UseLargePages to the command line to use
> hugepages it's even larger. So why must I incur this performance
> degradation if I simply want to control who may mmap hugepages out of the
> global pool?
Even if we end up having a seperate controller for hugetlb, we would need
some bits of memcg, like tracking page cgroup, moving page cgroup on
page offline. We will also be duplicating some amount of framework for
supporting cgroup removal etc, because all those code deal with struct
page (actually compound page )
-aneesh
next prev parent reply other threads:[~2012-05-04 18:29 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 6:11 inux-next: Tree for Apr 27 Stephen Rothwell
2012-04-27 15:47 ` inux-next: Tree for Apr 27 (uml + mm/memcontrol.c) Randy Dunlap
2012-04-27 18:44 ` David Rientjes
2012-04-27 20:23 ` Andrew Morton
2012-04-27 21:27 ` David Rientjes
2012-04-27 21:36 ` Andrew Morton
2012-04-27 23:14 ` David Rientjes
2012-04-27 23:24 ` Andrew Morton
2012-04-27 23:52 ` David Rientjes
2012-04-28 18:01 ` Aneesh Kumar K.V
2012-05-03 9:13 ` David Rientjes
2012-05-03 10:30 ` Hiroyuki Kamezawa
2012-05-03 20:56 ` David Rientjes
2012-05-03 21:57 ` David Rientjes
2012-05-03 23:21 ` Hiroyuki Kamezawa
2012-05-03 23:33 ` Hiroyuki Kamezawa
2012-05-04 18:29 ` Aneesh Kumar K.V [this message]
2012-05-03 23:17 ` Hiroyuki Kamezawa
2012-05-04 17:24 ` Tejun Heo
2012-05-07 14:01 ` Michal Hocko
2012-05-07 17:08 ` Tejun Heo
2012-05-08 10:48 ` Michal Hocko
2012-05-03 13:54 ` Aneesh Kumar K.V
2012-05-03 20:39 ` David Rientjes
2012-04-28 0:45 ` Randy Dunlap
[not found] ` <20120427161146.95422142968526faaff615d4-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2012-04-27 16:56 ` inux-next: Tree for Apr 27 (infiniband/hw/ocrdma) Randy Dunlap
[not found] ` <4F9ACFC4.6010002-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
2012-04-27 23:54 ` Roland Dreier
2012-05-02 22:51 ` [PATCH] RDMA/ocrdma: Fix build with IPV6=n Roland Dreier
[not found] ` <1335999060-23779-1-git-send-email-roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2012-05-03 0:29 ` Randy Dunlap
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=877gwryf4h.fsf@skywalker.in.ibm.com \
--to=aneesh.kumar@linux$(echo .)vnet.ibm.com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=kamezawa.hiroyu@jp$(echo .)fujitsu.com \
--cc=kamezawa.hiroyuki@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rdunlap@xenotime$(echo .)net \
--cc=richard@nod$(echo .)at \
--cc=rientjes@google$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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