From owner-freebsd-hackers@FreeBSD.ORG  Fri May 30 14:03:33 2003
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 410CA37B401
	for <hackers@freebsd.org>; Fri, 30 May 2003 14:03:33 -0700 (PDT)
Received: from mail.tel.fer.hr (zg06-080.dialin.iskon.hr [213.191.148.81])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E6A3143F3F
	for <hackers@freebsd.org>; Fri, 30 May 2003 14:03:31 -0700 (PDT)
	(envelope-from zec@tel.fer.hr)
Received: from tel.fer.hr (marko-tp.katoda.net [192.168.201.109])
	by mail.tel.fer.hr (8.12.6/8.12.6) with ESMTP id h4UL369W000519;
	Fri, 30 May 2003 23:03:11 +0200 (CEST)
	(envelope-from zec@tel.fer.hr)
Message-ID: <3ED7C714.9DE7BC07@tel.fer.hr>
Date: Fri, 30 May 2003 23:03:17 +0200
From: Marko Zec <zec@tel.fer.hr>
X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Sean Chittenden <sean@chittenden.org>
References: <3ED14BF3.139CAC32@tel.fer.hr>
	<20030530182645.GP62688@perrin.int.nxad.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: hackers@freebsd.org
Subject: Re: Network stack cloning / virtualization patches
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 30 May 2003 21:03:33 -0000

Sean Chittenden wrote:

> can it be broken down into a smaller set of commits?

No it can't. That's probably the biggest problem with the network stack
cloning concept - you can either properly virtualize the entire stack or do
no virtualization at all. Therefore even if I ever succeed in bringing the
patch in full sync with -CURRENT, I assume that many people would stand out
against it to be incorporated to the main source tree, as the patch would
significantly change pretty much of the code in the net* portions of the
kernel tree...

At the moment your best option is to try out the available version (against
4.8-R), report any bugs you encounter, and provide suggestions for further
reengineering...

Cheers,

Marko