From owner-freebsd-net@FreeBSD.ORG  Sat Sep 25 09:35:05 2004
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 0D97616A4CE
	for <freebsd-net@freebsd.org>; Sat, 25 Sep 2004 09:35:05 +0000 (GMT)
Received: from smtp05.web.de (smtp05.web.de [217.72.192.209])
	by mx1.FreeBSD.org (Postfix) with ESMTP id BE9F443D39
	for <freebsd-net@freebsd.org>; Sat, 25 Sep 2004 09:35:04 +0000 (GMT)
	(envelope-from Waldemar.Kornewald@web.de)
Received: from [80.134.95.235] (helo=[80.134.95.235])
	by smtp05.web.de with asmtp (TLSv1:RC4-MD5:128)
	(WEB.DE 4.101 #44)
	id 1CB8xL-0006zW-00
	for freebsd-net@freebsd.org; Sat, 25 Sep 2004 11:35:03 +0200
Message-ID: <41553B70.409@web.de>
Date: Sat, 25 Sep 2004 11:33:36 +0200
From: Waldemar Kornewald <Waldemar.Kornewald@web.de>
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: FreeBSD-net <freebsd-net@freebsd.org>
References: <Pine.NEB.3.96L.1040924140514.82478J-100000@fledge.watson.org>
In-Reply-To: <Pine.NEB.3.96L.1040924140514.82478J-100000@fledge.watson.org>
X-Enigmail-Version: 0.86.1.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: Waldemar.Kornewald@web.de
X-Sender: Waldemar.Kornewald@web.de
Subject: Re: locking
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Sep 2004 09:35:05 -0000

Robert Watson wrote:
> There are some sections of the network stack, such as the KAME IPSEC
> implementation, parts of IPv6, and some device drivers, which are not yet
> completely MPSAFE.  This may or may not be an issue depending on what
> your requirements are.  If you have any bug fixes or improvements, we
> would love to hear about them -- right now our locking is fairly
> coarse-grained but we'll be looking at contention issues over the next few
> months to see how best to refine our locking strategy.

We wanted to have fine-grained locking (BeOS/Haiku emphasizes on 
threading very much), but at least having some locking is better than 
our current situation (nearly no locking ;). Our first aim is to get a 
stable modularized netstack, finally. The next steps would be 
fine-grained locking and maybe trying out iovecs instead of mbufs.
Having IPv4 ready is a good start. IPv6 is not too urgent at the moment.

Bye,
Waldemar Kornewald