From owner-p4-projects@FreeBSD.ORG Tue Apr 28 18:23:50 2009 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 1A9D71065676; Tue, 28 Apr 2009 18:23:50 +0000 (UTC) Delivered-To: perforce@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CEB2F1065674 for ; Tue, 28 Apr 2009 18:23:49 +0000 (UTC) (envelope-from zec@freebsd.org) Received: from labs4.cc.fer.hr (labs4.cc.fer.hr [161.53.72.24]) by mx1.freebsd.org (Postfix) with ESMTP id 5E50E8FC17 for ; Tue, 28 Apr 2009 18:23:48 +0000 (UTC) (envelope-from zec@freebsd.org) Received: from sluga.fer.hr (sluga.cc.fer.hr [161.53.72.14]) by labs4.cc.fer.hr (8.14.2/8.14.2) with ESMTP id n3SI7p6e013949 for ; Tue, 28 Apr 2009 20:07:51 +0200 (CEST) Received: from [192.168.200.111] ([161.53.19.79]) by sluga.fer.hr over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Tue, 28 Apr 2009 20:07:30 +0200 From: Marko Zec To: Julian Elischer Date: Tue, 28 Apr 2009 20:07:24 +0200 User-Agent: KMail/1.9.10 References: <200904281751.n3SHpTWw007937@repoman.freebsd.org> <49F74413.3090002@elischer.org> In-Reply-To: <49F74413.3090002@elischer.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200904282007.24852.zec@freebsd.org> X-OriginalArrivalTime: 28 Apr 2009 18:07:30.0578 (UTC) FILETIME=[325C0F20:01C9C82C] X-Scanned-By: MIMEDefang 2.64 on 161.53.72.24 Cc: Perforce Change Reviews Subject: Re: PERFORCE change 161261 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Apr 2009 18:23:51 -0000 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