From: Daniel Lezcano <daniel.lezcano-GANU6spQydw@public.gmane.org>
To: "Eric W. Biederman" <ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
Cc: Linux Containers <containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: Re: Progress of containers at 2.6.32/33?
Date: Tue, 23 Feb 2010 13:32:15 +0100 [thread overview]
Message-ID: <4B83CACF.5010701@free.fr> (raw)
In-Reply-To: <m1r5oepjye.fsf-+imSwln9KH6u2/kzUuoCbdi2O/JbrIOy@public.gmane.org>
Eric W. Biederman wrote:
> 2.6.32 is likely to be used widely so I expect everyone's out of tree
> patches to be updated. As a metric to figuring out which things have
> worked and which things have not I would like ask all of those who are
> maintaining out of tree container patches to give some feedback on
> what code they have been able to remove from their patchsets when
> using the latest kernel, and which patches persist.
>
> I have been in some conversations lately that indicate that we have
> some tremendous short comings in the work that has gone on in the
> public tree. So I am asking now so we can guage where we are at
> as a community.
>
Do you consider the checkpoint / restart is part of the container progress ?
I am asking that because there are some cases where the container should
be more virtualized if the CR is to be take into account.
For example, the network devices index is not virtualized in a
container, this is not a problem without the CR. But with it, we won't
support any application binding to a device or using a device index.
prev parent reply other threads:[~2010-02-23 12:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m1r5oepjye.fsf@fess.ebiederm.org>
[not found] ` <m1r5oepjye.fsf-+imSwln9KH6u2/kzUuoCbdi2O/JbrIOy@public.gmane.org>
2010-02-22 14:58 ` Progress of containers at 2.6.32/33? Serge E. Hallyn
2010-02-23 12:32 ` Daniel Lezcano [this message]
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=4B83CACF.5010701@free.fr \
--to=daniel.lezcano-ganu6spqydw@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@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.