From owner-freebsd-arch@FreeBSD.ORG  Tue Aug 19 21:09:27 2003
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 168D016A4BF; Tue, 19 Aug 2003 21:09:27 -0700 (PDT)
Received: from ebb.errno.com (ebb.errno.com [66.127.85.87])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 47E7B43F93; Tue, 19 Aug 2003 21:09:26 -0700 (PDT)
	(envelope-from sam@errno.com)
Received: from melange.errno.com (melange.errno.com [66.127.85.82])
	(authenticated bits=0)
	by ebb.errno.com (8.12.9/8.12.9) with ESMTP id h7K49N7N023724
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 19 Aug 2003 21:09:25 -0700 (PDT)
	(envelope-from sam@errno.com)
Date: Tue, 19 Aug 2003 21:09:35 -0700
From: Sam Leffler <sam@errno.com>
To: Scott Long <scottl@freebsd.org>
Message-ID: <466057615.1061327374@melange.errno.com>
In-Reply-To: <3F42D8EC.1010706@freebsd.org>
References: <447450569.1061308767@melange.errno.com>
 <3F42D8EC.1010706@freebsd.org>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
cc: freebsd-net@freebsd.org
cc: freebsd-arch@freebsd.org
Subject: Re: HEADS UP: network locking work going on
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussion related to FreeBSD architecture
	<freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Aug 2003 04:09:27 -0000

> Is there any consideration for running some hardware drivers with Giant
> while they are converted?

I have seen no issues so far mixing drivers w/ and w/o Giant.  But that 
won't be true once drivers stop inheriting Giant when entered "from the 
top".  It's not clear to me that it's any more work to lock drivers than to 
provide some sort of compatibility shims.  Regardless this won't be an 
issue for a while.

Mind you I am still tracking at least one nasty bug...

	Sam