From: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"balbir@linux.vnet.ibm.com" <balbir@linux.vnet.ibm.com>,
randy.dunlap@oracle.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
Subject: Re: [PATCH] memcg: update documentation v3
Date: Fri, 9 Apr 2010 11:11:45 +0900 [thread overview]
Message-ID: <20100409111145.5359a872.nishimura@mxp.nes.nec.co.jp> (raw)
In-Reply-To: <20100409104556.2aa6399d.kamezawa.hiroyu@jp.fujitsu.com>
On Fri, 9 Apr 2010 10:45:56 +0900, KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> On Fri, 9 Apr 2010 10:26:26 +0900
> Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp> wrote:
> > > +Current Status: linux-2.6.34-mmotm(development version of 2010/April)
> > > +
> > > +Features:
> > > + - accounting anonymous pages, file caches, swap caches usage and limit them.
> > > + - private LRU and reclaim routine. (system's global LRU and private LRU
> > > + work independently from each other)
> > > + - optionally, memory+swap usage can be accounted and limited.
> > > + - hierarchical accounting
> > > + - soft limit
> > > + - moving(recharging) account at moving a task is selectable.
> > > + - usage threshold notifier
> > > + - oom-killer disable knob and oom-notifier
> > > + - Root cgroup has no limit controls.
> > > +
> > > + Kernel memory and Hugepages are not under control yet. We just manage
> > > + pages on LRU. To add more controls, we have to take care of performance.
> > > +
> > > +Brief summary of control files.
> > > +
> > > + tasks # attach a task(thread)
> > > + cgroup.procs # attach a process(all threads under it)
> > IIUC, writing to cgroup.procs isn't supported yet. So, I think we don't have to
> > bother explaining cgroup.procs here.
> >
>
> It's supported. See Documetaion/cgroup/cgroup.txt
> IIRC, I use cgroup.procs file for migrating, sometimes.
>
I can't write to it now.
# echo $$ >/cgroup/memory/01/cgroup.procs
-bash: echo: write error: Invalid argument
# ls -l /cgroup/memory/01/cgroup.procs
-r--r--r-- 1 root root 0 2010-04-09 10:41 /cgroup/memory/01/cgroup.procs
# uname -a
Linux GibsonE 2.6.34-rc3-mm1-00432-g37c11f5 #1 SMP Thu Apr 8 11:03:39 JST 2010 x86_64 x86_64 x86_64 GNU/Linux
And kernel/cgroup.c says:
3161 {
3162 .name = CGROUP_FILE_GENERIC_PREFIX "procs",
3163 .open = cgroup_procs_open,
3164 /* .write_u64 = cgroup_procs_write, TODO */
3165 .release = cgroup_pidlist_release,
3166 .mode = S_IRUGO,
3167 },
IIRC, it's supported once, but the patch was dropped.
Thanks,
Daisuke Nishimura.
--
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:[~2010-04-09 2:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 5:58 KAMEZAWA Hiroyuki
2010-04-08 17:32 ` Randy Dunlap
2010-04-08 23:50 ` KAMEZAWA Hiroyuki
2010-04-09 1:26 ` Daisuke Nishimura
2010-04-09 1:45 ` KAMEZAWA Hiroyuki
2010-04-09 2:11 ` Daisuke Nishimura [this message]
2010-04-09 3:01 ` KAMEZAWA Hiroyuki
2010-04-09 4:45 ` [PATCH] memcg: update documentation v4 KAMEZAWA Hiroyuki
2010-04-09 5:50 ` Daisuke Nishimura
2010-04-09 17:04 ` Randy Dunlap
2010-04-13 4:45 ` [PATCH] memcg: update documentation v5 KAMEZAWA Hiroyuki
2010-04-13 6:04 ` Balbir Singh
2010-04-13 6:20 ` KAMEZAWA Hiroyuki
2010-04-13 6:48 ` Balbir Singh
2010-04-13 6:58 ` [PATCH] memcg: update documentation v6 KAMEZAWA Hiroyuki
2010-04-13 15:54 ` Randy Dunlap
2010-04-14 1:22 ` [PATCH] memcg: update documentation v7 KAMEZAWA Hiroyuki
2010-04-14 18:11 ` Randy Dunlap
2010-04-15 0:34 ` [PATCH] memcg: update documentation v8 KAMEZAWA Hiroyuki
2010-04-15 15:48 ` Randy Dunlap
2010-04-13 13:57 ` [PATCH] memcg: update documentation v5 Vivek Goyal
2010-04-13 14:03 ` Vivek Goyal
2010-04-13 15:08 ` Balbir Singh
2010-04-13 15:16 ` Vivek Goyal
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=20100409111145.5359a872.nishimura@mxp.nes.nec.co.jp \
--to=nishimura@mxp.nes.nec.co.jp \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=randy.dunlap@oracle.com \
/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