[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.1205301831270.25774@chino.kir.corp.google.com>
Date: Wed, 30 May 2012 18:31:41 -0700 (PDT)
From: David Rientjes <rientjes@...gle.com>
To: Kamezawa Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
cc: KOSAKI Motohiro <kosaki.motohiro@...il.com>,
Gao feng <gaofeng@...fujitsu.com>, hannes@...xchg.org,
mhocko@...e.cz, bsingharora@...il.com, akpm@...ux-foundation.org,
linux-kernel@...r.kernel.org, cgroups@...r.kernel.org,
linux-mm@...ck.org, containers@...ts.linux-foundation.org
Subject: Re: [PATCH] meminfo: show /proc/meminfo base on container's memcg
On Thu, 31 May 2012, Kamezawa Hiroyuki wrote:
> > > My test with sysfs node's meminfo seems to work...
> > >
> > > [root@...00-1 qqm]# mount --bind /sys/devices/system/node/node0/meminfo
> > > /proc/meminfo
> > > [root@...00-1 qqm]# cat /proc/meminfo
> > >
> > > Node 0 MemTotal: 8379636 kB
> >
> > This doesn't seem like a good idea unless the application supports the
> > "Node 0" prefix in /proc/meminfo.
> >
> Of course, /cgroup/memory/..../memory.meminfo , a new file, will use the same
> format of /proc/meminfo. Above is just an example of bind-mount.
>
It's not just a memcg issue, it would also be a cpusets issue.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists