From owner-freebsd-net@FreeBSD.ORG Sat Jun 23 06:06:53 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 43D9916A421 for ; Sat, 23 Jun 2007 06:06:53 +0000 (UTC) (envelope-from freebsd-net@dino.sk) Received: from bsd.dino.sk (bsd.dino.sk [213.215.72.60]) by mx1.freebsd.org (Postfix) with ESMTP id CA8FE13C4AD for ; Sat, 23 Jun 2007 06:06:52 +0000 (UTC) (envelope-from freebsd-net@dino.sk) Received: from fox.dino.sk (home.dino.sk [84.245.95.252]) (AUTH: PLAIN milan, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by bsd.dino.sk with esmtp; Sat, 23 Jun 2007 07:58:48 +0200 id 0000005A.467CB698.00011227 From: Milan Obuch To: freebsd-net@freebsd.org Date: Sat, 23 Jun 2007 07:54:22 +0200 User-Agent: KMail/1.9.6 References: <467C1E3C.1020203@elischer.org> <467C5EEC.1000208@icir.org> <467C6B79.4080304@elischer.org> In-Reply-To: <467C6B79.4080304@elischer.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200706230754.23148.freebsd-net@dino.sk> Subject: Re: Vimage virtual networking and 7.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Jun 2007 06:06:53 -0000 On Saturday 23 June 2007, Julian Elischer wrote: > Bruce M. Simpson wrote: > > Julian Elischer wrote: > >> In the future I am hoping to be able to use vimage in our products. > >> They are based at the moment on 6.1, but I can see in a year they will > >> be based on 7.x. > >> > >> Patches for 7.0 and vimage are currently available in perforce. > >> What I would like to see is if there are any parts of that patch that > >> would allow us to make adding of vimage to 7.1 an easier task. > >> ... > > > > I think there are deeper issues in the network stack overall which need > > to be addressed, such as our lack of support for multipathing, scoped > > addresses, and all the tidyups which need to happen in struct ifnet to > > deal with this. > > > > My concern is that vimage may be a very intrusive change indeed where > > these matters are concerned, unless the vimage patches are being kept > > up-to-date and regression tested as issues are resolved and new features > > added. > > This is axectly why I think they should go in now. > Remembering that they compile out to non changes.. > > Marko will I believe continue to keep up with -current as changes are made > there. however it would be easier if they were in the tree so that people > MAKING the new changes just took it into account when they did it. > > Similarly it will be a lot harder to backport to 7.x unless we keep a a > separate 7.x + vimage branch in p4 however that means that marko will need > to do everything twice. > I used old 4.x based vimage for some time. Now I would like to see vimage as an option in 7.x - I need this functionality again. I keep testing it as time permits, but having it in the main tree would make this for me a lot easier. When 7.0 becomes release, divergence begins, and this just multiplies effort needed to keep anything with vimage in good shape. With no option vimage, current state is kept, as far as I can see and understand the whole thing, so I think it should go in, now. Regards, Milan -- This address is used only for mailing list response. Do not send any personal messages to it, use milan in address instead.