From owner-freebsd-current@FreeBSD.ORG Tue Mar 2 13:08:57 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DFA5716A4CE for ; Tue, 2 Mar 2004 13:08:57 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CB3E43D2F for ; Tue, 2 Mar 2004 13:08:57 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 94877 invoked from network); 2 Mar 2004 21:08:56 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 2 Mar 2004 21:08:56 -0000 Message-ID: <4044F7E7.EB1CC703@freebsd.org> Date: Tue, 02 Mar 2004 22:08:55 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: "Bjoern A. Zeeb" References: <4043B6BA.B847F081@freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: My planned work on networking stack X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Mar 2004 21:08:58 -0000 "Bjoern A. Zeeb" wrote: > > On Mon, 1 Mar 2004, Andre Oppermann wrote: > > Hi, > > > I put this up for coordination and cooperation in my planned work on the > > FreeBSD networking system. This is my todo list of things I want to do > > from now through summer 04. If you are or intend to work on one of these > > please step forward so we can coordinate. :-) > ... > > [] other stuff that I happen to stumble over... ;-) > > I still have in mind that I would like to see vimage[1] in HEAD one day > ... I think it would be a pretty cool feature to have. If one can keep > this in mind when doing greater modelling on the network stack it > might help the one who will - at some time - find the time to > ingtegrate it. I have seen your work and it is very interesting from a research point of view. For a normal kernel I don't see any benefit to it. Often jails are pointed out for it but I don't think this really makes sense. If you go as far as giving each jail it's own network stack including routing (what for in a jail?) then you can make the full leap and do something like userland BSD akin the userland Linux. Then each jail gets it's own fully virtualized machine. Makes more sense to me than just giving them a network stack on their own. Don't get me wrong, it's very cool but the net benefit and usefulness in realworld situations is pretty small. -- Andre