From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Balbir Singh <balbir@linux.vnet.ibm.com>
Cc: Linux Containers <containers@lists.osdl.org>, libvir-list@redhat.com
Subject: Re: [libvirt] kernel summit topic - 'containers end-game'
Date: Tue, 30 Jun 2009 15:06:13 -0500 [thread overview]
Message-ID: <20090630200613.GA22283@us.ibm.com> (raw)
In-Reply-To: <661de9470906290335i74f76a55t57438a781e6a84c8@mail.gmail.com>
Quoting Balbir Singh (balbir@linux.vnet.ibm.com):
> On Tue, Jun 23, 2009 at 8:26 PM, Serge E. Hallyn<serue@us.ibm.com> wrote:
> > A topic on ksummit agenda is 'containers end-game and how do we
> > get there'.
> >
> > So for starters, looking just at application (and system) containers, what do
> > the libvirt and liblxc projects want to see in kernel support that is currently
> > missing? Are there specific things that should be done soon to make containers
> > more useful and usable?
> >
> > More generally, the topic raises the question... what 'end-games' are there?
> > A few I can think of off-hand include:
> >
> > 1. resource control
>
> We intend to hold a io-controller minisummit before KS, we should have
> updates on that front. We also need to discuss CPU hard limits and
> Memory soft limits. We need control for memory large page, mlock, OOM
> notification support, shared page accounting, etc. Eventually on the
> libvirt front, we want to isolate cgroup and lxc support into
> individual components (long term)
Thanks, Balbir. By the last sentence, are you talking about having
cgroup in its own libcgroup, or do you mean something else?
On the topic of cgroups, does anyone not agree that we should try
to get rid of the ns cgroup, at least once user namespaces can
prevent root in a container from escaping their cgroup?
thanks,
-serge
next prev parent reply other threads:[~2009-06-30 20:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 14:56 kernel summit topic - 'containers end-game' Serge E. Hallyn
2009-06-29 10:35 ` [libvirt] " Balbir Singh
2009-06-30 20:06 ` Serge E. Hallyn [this message]
2009-07-01 4:29 ` Balbir Singh
[not found] ` <20090630200613.GA22283-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-07-02 16:58 ` Daniel Lezcano
2009-07-02 16:43 ` [libvirt] " Daniel Lezcano
[not found] ` <4A4CE3A6.200-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2009-07-02 18:27 ` Oren Laadan
2009-07-06 14:51 ` [libvirt] " Serge E. Hallyn
2009-07-08 7:55 ` Daniel Lezcano
2009-07-08 13:45 ` Serge E. Hallyn
[not found] ` <20090623145611.GB19332-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-07-02 18:38 ` Oren Laadan
2009-07-06 14:34 ` [libvirt] " Serge E. Hallyn
[not found] ` <20090706143401.GA16868-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-07-06 17:30 ` Oren Laadan
2009-07-06 18:48 ` [libvirt] " Serge E. Hallyn
[not found] ` <20090706184848.GA23819-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-07-07 15:36 ` Oren Laadan
[not found] ` <4A536B91.5010205-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2009-07-07 16:14 ` Serge E. Hallyn
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=20090630200613.GA22283@us.ibm.com \
--to=serue@us.ibm.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=containers@lists.osdl.org \
--cc=libvir-list@redhat.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 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.