[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090213222818.GA17630@x200.localdomain>
Date: Sat, 14 Feb 2009 01:28:18 +0300
From: Alexey Dobriyan <adobriyan@...il.com>
To: Ingo Molnar <mingo@...e.hu>
Cc: Dave Hansen <dave@...ux.vnet.ibm.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Matt Mackall <mpm@...enic.com>,
containers@...ts.linux-foundation.org, hpa@...or.com,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
viro@...iv.linux.org.uk, linux-api@...r.kernel.org,
torvalds@...ux-foundation.org, tglx@...utronix.de,
Pavel Emelyanov <xemul@...nvz.org>
Subject: Re: What can OpenVZ do?
On Fri, Feb 13, 2009 at 12:45:03PM +0100, Ingo Molnar wrote:
>
> * Alexey Dobriyan <adobriyan@...il.com> wrote:
>
> > On Fri, Feb 13, 2009 at 11:27:32AM +0100, Ingo Molnar wrote:
> > > Merging checkpoints instead might give them the incentive to get
> > > their act together.
> >
> > Knowing how much time it takes to beat CPT back into usable shape every time
> > big kernel rebase is done, OpenVZ/Virtuozzo have every single damn incentive
> > to have CPT mainlined.
>
> So where is the bottleneck? I suspect the effort in having forward ported
> it across 4 major kernel releases in a single year is already larger than
> the technical effort it would take to upstream it. Any unreasonable upstream
> resistence/passivity you are bumping into?
People were busy with netns/containers stuff and OpenVZ/Virtuozzo bugs.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists