From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>,
akpm@linux-foundation.org, LKML <linux-kernel@vger.kernel.org>,
"Kirill A. Shutemov" <kirill@shutemov.name>
Subject: Re: [PATCH -mmotm] memcg: implement memory thresholds document fixes
Date: Thu, 7 Jan 2010 14:24:19 +0530 [thread overview]
Message-ID: <20100107085419.GV3059@balbir.in.ibm.com> (raw)
In-Reply-To: <20100107104018.6fdb2f79.kamezawa.hiroyu@jp.fujitsu.com>
* KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> [2010-01-07 10:40:18]:
> > (My biggest concern now is the influence of transparent hugepage to vm and memcg.)
> >
> Yes, it's interesting challenge but has concerns for us ;)
>
Yes, I agree. I spoke to Andrea and he said that transparent pages
should not affect us much directly. He also added support for memcg,
but this is definitely something we should watch for.
--
Balbir
next prev parent reply other threads:[~2010-01-07 8:54 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 22:34 mmotm 2010-01-06-14-34 uploaded akpm
2010-01-07 0:57 ` [PATCH -mmotm] memcg: implement memory thresholds document fixes Daisuke Nishimura
2010-01-07 1:18 ` KAMEZAWA Hiroyuki
2010-01-07 1:34 ` Daisuke Nishimura
2010-01-07 1:40 ` KAMEZAWA Hiroyuki
2010-01-07 8:54 ` Balbir Singh [this message]
2010-01-07 8:52 ` Balbir Singh
2010-01-07 9:04 ` KAMEZAWA Hiroyuki
2010-01-07 6:29 ` Kirill A. Shutemov
2010-01-07 1:08 ` mmotm 2010-01-06-14-34 uploaded (kernel/cgroup) Randy Dunlap
2010-01-07 2:31 ` KAMEZAWA Hiroyuki
2010-01-07 2:41 ` Li Zefan
2010-01-07 2:47 ` KAMEZAWA Hiroyuki
2010-01-07 3:04 ` Li Zefan
2010-01-07 16:47 ` Randy Dunlap
2010-01-07 17:29 ` Kirill A. Shutemov
2010-01-07 1:10 ` mmotm 2010-01-06-14-34 uploaded (mm/memcontrol) Randy Dunlap
2010-01-07 2:13 ` Daisuke Nishimura
2010-01-07 2:21 ` KAMEZAWA Hiroyuki
2010-01-07 2:59 ` Daisuke Nishimura
2010-01-07 3:02 ` KAMEZAWA Hiroyuki
2010-01-07 4:06 ` [PATCH -mmotm] build fix for memcg-move-charges-of-anonymous-swap.patch Daisuke Nishimura
2010-01-07 4:30 ` KAMEZAWA Hiroyuki
2010-01-07 5:07 ` KAMEZAWA Hiroyuki
2010-01-07 5:14 ` Daisuke Nishimura
2010-01-07 5:52 ` KAMEZAWA Hiroyuki
2010-01-07 11:23 ` How should we handle CONFIG_CGROUP_MEM_RES_CTRL_SWAP (Re: [PATCH -mmotm] build fix for memcg-move-charges-of-anonymous-swap.patch) Daisuke Nishimura
2010-01-07 12:38 ` Balbir Singh
2010-01-07 4:06 ` [PATCH -mmotm] build fix for memcg-improve-performance-in-moving-swap-charge.patch Daisuke Nishimura
2010-01-07 4:31 ` KAMEZAWA Hiroyuki
2010-01-07 3:48 ` mmotm 2010-01-06-14-34 uploaded Valdis.Kletnieks
2010-01-07 4:01 ` Valdis.Kletnieks
2010-01-07 16:04 ` mmotm 2010-01-06-14-34 uploaded (squashfs+lib/decomp) Randy Dunlap
2010-01-08 6:54 ` Valdis.Kletnieks
2010-01-08 16:37 ` Randy Dunlap
2010-01-07 17:13 ` mmotm 2010-01-06-14-34 uploaded Randy Dunlap
2010-01-08 22:21 ` mmotm 2010-01-06-14-34 - crash in CPUfreq Valdis.Kletnieks
2010-01-11 15:39 ` Minchan Kim
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=20100107085419.GV3059@balbir.in.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=nishimura@mxp.nes.nec.co.jp \
/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
Powered by JetHome