Date: Tue, 28 Apr 2009 20:07:24 +0200 From: Marko Zec <zec@freebsd.org> To: Julian Elischer <julian@elischer.org> Cc: Perforce Change Reviews <perforce@freebsd.org> Subject: Re: PERFORCE change 161261 for review Message-ID: <200904282007.24852.zec@freebsd.org> In-Reply-To: <49F74413.3090002@elischer.org> References: <200904281751.n3SHpTWw007937@repoman.freebsd.org> <49F74413.3090002@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 28 April 2009 19:59:47 Julian Elischer wrote: > Marko Zec wrote: > > http://perforce.freebsd.org/chv.cgi?CH=161261 > > > > Change 161261 by zec@zec_amdx2 on 2009/04/28 17:51:16 > > > > Unbreak in_rtqtimo(). > > so, If I'm right, > the plan is: > > commit vimage-commit, with one single vimage > leave to simmer for a week while people test > commit vimage-commit2.. in time for BSDCan.. Yup that's the plan, the sooner the better I'd say... The code in vimage-commit2 is limited to a single vnet instance as well, but the curvnet there is thread-local, and is being set / cleared where appropriate. So we will need another commit to add the ability to instantiate multiple vnets and assign interfaces from one to another, but this would be pretty trivial to port from the vimage branch, unless we want to hold on the ball and rething our management interfaces and vnet / jail integration in general, which I believe we do... > Oh this is so exciting.. :-) Well once the bugs start popping out, and people start to discover that many subsystems are not yet VIMAGE-compliant, it will become exciting indeed :) Marko
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200904282007.24852.zec>