From: Li Zefan <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
To: Marian Marinov <mm-NV7Lj0SOnH0@public.gmane.org>
Cc: lxc-devel-cunTk1MwBs9qMoObBWhMNEqPaTDuhLve2LY78lusg7I@public.gmane.org,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"Daniel P. Berrange"
<berrange-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Serge Hallyn
<serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>
Subject: Re: RFC: cgroups aware proc
Date: Tue, 7 Jan 2014 19:16:50 +0800 [thread overview]
Message-ID: <52CBE222.9030404@huawei.com> (raw)
In-Reply-To: <52C8A36B.6030201-NV7Lj0SOnH0@public.gmane.org>
On 2014/1/5 8:12, Marian Marinov wrote:
> Happy new year guys.
>
> I need to have /proc cgroups aware, as I want to have LXC containers that see only the resources that are given to them.
>
> In order to do that I had to patch the kernel. I decided to start with cpuinfo, stat and interrupts and then continue
> with meminfo and loadavg.
>
> I managed to patch the Kernel (linux 3.12.0) and make /proc/cpuinfo, /proc/stat and /proc/interrupts be cgroups aware.
>
> Attached are the patches that make the necessary changes.
>
> The change for /proc/cpuinfo and /proc/interrupts is currently done only for x86 arch, but I will patch the rest of the
> architectures if the style of the patches is acceptable.
>
> Tomorrow I will check if the patches apply and build with the latest kernel.
>
People tried to do this before, but got rejected by upstream maintainers,
and then the opinion was to do this in userspace throught FUSE.
Seems libvirt already supports containerized /proc/meminfo in this way.
See:
http://libvirt.org/drvlxc.html
next prev parent reply other threads:[~2014-01-07 11:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <529350DB.3010906@yuhu.biz>
[not found] ` <20131125150940.GB7120@sergelap>
[not found] ` <20131125151232.GR6766@redhat.com>
[not found] ` <52937B0C.3070005@yuhu.biz>
[not found] ` <52937B0C.3070005-NV7Lj0SOnH0@public.gmane.org>
2014-01-04 4:28 ` RFC: cgroups aware proc Marian Marinov
[not found] ` <52C78E09.60904-NV7Lj0SOnH0@public.gmane.org>
2014-01-05 0:12 ` Marian Marinov
[not found] ` <52C8A36B.6030201-NV7Lj0SOnH0@public.gmane.org>
2014-01-07 11:16 ` Li Zefan [this message]
2014-01-07 11:17 ` Li Zefan
[not found] ` <52CBE22F.1010106-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2014-01-07 17:42 ` Marian Marinov
[not found] ` <52CC3C80.8030603-NV7Lj0SOnH0@public.gmane.org>
2014-01-08 15:27 ` Serge Hallyn
2014-01-10 16:29 ` Marian Marinov
2014-01-13 3:26 ` Li Zefan
[not found] ` <52D41316.5080508@yuhu.biz>
2014-01-13 17:12 ` Fwd: " Peter Zijlstra
[not found] ` <20140113171238.GS31570-ndre7Fmf5hadTX5a5knrm8zTDFooKrT+cvkQGrU6aU0@public.gmane.org>
2014-01-14 0:58 ` Marian Marinov
2014-01-14 0:58 ` Marian Marinov
[not found] ` <52D48BA6.2080701-NV7Lj0SOnH0@public.gmane.org>
2014-01-14 10:05 ` Peter Zijlstra
2014-01-14 10:05 ` Peter Zijlstra
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=52CBE222.9030404@huawei.com \
--to=lizefan-hv44wf8li93qt0dzr+alfa@public.gmane.org \
--cc=berrange-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lxc-devel-cunTk1MwBs9qMoObBWhMNEqPaTDuhLve2LY78lusg7I@public.gmane.org \
--cc=mm-NV7Lj0SOnH0@public.gmane.org \
--cc=serge.hallyn-GeWIH/nMZzLQT0dZR+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.