From: Daniel Lezcano <daniel.lezcano-GANU6spQydw@public.gmane.org>
To: Linux Containers
<containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
Balbir Singh1
<balbir.singh-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org>,
Paul Menage <menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Subject: cgroup information proc file format
Date: Thu, 11 Aug 2011 22:55:31 +0200 [thread overview]
Message-ID: <4E4441C3.5020603@free.fr> (raw)
Hi all,
the cgroup cpuset and memory reduce access to a part of the resources on
the system. Some applications use the /proc/cpuinfo and /proc/meminfo to
allocate the resources. For instance, HPC jobs look at /proc/cpuinfo to
fork the number of cpu found in this file either look at /proc/meminfo
to allocate a big chunk of memory. Each process set the affinity on each
cpu, which in case a subset of cpus is used, some affinity will fail.
In the case of the container, the cgroup is used to reduce the memory or
to assign a cpu to the container. Unfortunately, as this partitioning is
not reflected in /proc, the different system tools (ps, top, free, ...)
show a wrong information.
I was wondering if that would make sense to create for the different
cgroup subsystem, when it is relevant, a proc formatted file we can bind
mount /proc.
For example: /cgroup/memory.proc and /cgroup/cpuset.proc
Any ideas ?
-- Daniel
next reply other threads:[~2011-08-11 20:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 20:55 Daniel Lezcano [this message]
[not found] ` <4E4441C3.5020603-GANU6spQydw@public.gmane.org>
2011-08-11 21:30 ` cgroup information proc file format Glauber Costa
[not found] ` <4E4449F5.3010909-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2011-08-11 21:45 ` Daniel Lezcano
[not found] ` <4E444D96.7080206-GANU6spQydw@public.gmane.org>
2011-08-11 21:52 ` Serge Hallyn
2011-10-03 8:15 ` Glauber Costa
2011-10-04 2:42 ` Serge E. Hallyn
2011-10-04 6:17 ` Glauber Costa
2011-10-04 14:05 ` Serge Hallyn
2011-10-05 7:47 ` Glauber Costa
2011-10-06 12:50 ` Serge E. Hallyn
2011-08-11 22:58 ` Glauber Costa
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=4E4441C3.5020603@free.fr \
--to=daniel.lezcano-ganu6spqydw@public.gmane.org \
--cc=balbir.singh-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.