From: atp <Andrew.Phillips-xheW4WVAX9Y@public.gmane.org>
To: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: cpu shielding.
Date: Tue, 07 Feb 2012 09:02:54 +0000 [thread overview]
Message-ID: <1328605374.25682.5.camel@foo> (raw)
In-Reply-To: <20120207021527.GA17937@sergelap>
Serge,
> I'm afraid I haven't been following recent upstream discussions on
> this, but there are other people who want proc to show cgroup-limited
> information. See for instance http://lwn.net/Articles/460310/ . Glauber
> has also brought this up since then. I'd recommend pinging him.
>
> I'm all for /proc showing cgroup-filtered information, unconditionally.
>
I'll check with him, and report back. Having looked at how openvz
handles this, it seems that to do this comprehensively - even just for
cpu shielding is not a quick fix.
Andy
--
Andrew Phillips
Head of Systems
Direct: +44 (0)203 192 2509
Mobile: +44 (0)7595 242 900
LMAX, Yellow Building, 1A Nicholas Road, London, W11 4AN
The information in this e-mail and any attachment is confidential and is intended only for the named recipient(s). The e-mail may not be disclosed or used by any person other than the addressee, nor may it be copied in any way. If you are not a named recipient please notify the sender immediately and delete any copies of this message. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Any view or opinions presented are solely those of the author and do not necessarily represent those of the company.
next prev parent reply other threads:[~2012-02-07 9:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 13:50 cpu shielding atp
2012-02-07 2:15 ` Serge Hallyn
2012-02-07 9:02 ` atp [this message]
2012-02-07 10:35 ` Glauber Costa
2012-02-07 3:25 ` Zhu Yanhai
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=1328605374.25682.5.camel@foo \
--to=andrew.phillips-xhew4wvax9y@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@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.