From owner-freebsd-net@FreeBSD.ORG  Tue Aug 19 22:22:43 2003
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 B1AB216A4BF
	for <freebsd-net@FreeBSD.org>; Tue, 19 Aug 2003 22:22:43 -0700 (PDT)
Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0935343F3F
	for <freebsd-net@FreeBSD.org>; Tue, 19 Aug 2003 22:22:43 -0700 (PDT)
	(envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
	by gw.catspoiler.org (8.12.9/8.12.9) with ESMTP id h7K5MOM7032499;
	Tue, 19 Aug 2003 22:22:28 -0700 (PDT)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <200308200522.h7K5MOM7032499@gw.catspoiler.org>
Date: Tue, 19 Aug 2003 22:22:24 -0700 (PDT)
From: Don Lewis <truckman@FreeBSD.org>
To: sam@errno.com
In-Reply-To: <448579583.1061309896@melange.errno.com>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
cc: freebsd-net@FreeBSD.org
Subject: Re: HEADS UP: network locking work going on
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: Wed, 20 Aug 2003 05:22:44 -0000

On 19 Aug, Sam Leffler wrote:

> Once the work on the lower layer is stable I'll be turning my attention to 
> the upper layers of the network and to IPv6 and NFS.  There's plenty of 
> work to go around, so if you're interested in participating please let me 
> know.

BTW, there is a buf vs. vnode locking problem in nfssvc_iod() that I
haven't found a good fix for.  The code currently just leaves the vnode
unlocked.

I may have some time to work on this stuff in a month or so.