From owner-freebsd-current@FreeBSD.ORG  Mon Oct  4 05:11:35 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 DAA3A16A4CE; Mon,  4 Oct 2004 05:11:35 +0000 (GMT)
Received: from harmony.village.org (rover.village.org [168.103.84.182])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 5AD6A43D2F; Mon,  4 Oct 2004 05:11:35 +0000 (GMT)
	(envelope-from imp@bsdimp.com)
Received: from localhost (harmony.village.org [10.0.0.6])
	by harmony.village.org (8.13.1/8.13.1) with ESMTP id i945Aagv084183;
	Sun, 3 Oct 2004 23:10:37 -0600 (MDT)
	(envelope-from imp@bsdimp.com)
Date: Sun, 03 Oct 2004 23:12:09 -0600 (MDT)
Message-Id: <20041003.231209.04694657.imp@bsdimp.com>
To: phk@phk.freebsd.dk
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <48733.1096570677@critter.freebsd.dk>
References: <200409301409.25904.jhb@FreeBSD.org>
	<48733.1096570677@critter.freebsd.dk>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: freebsd-current@freebsd.org
cc: current@freebsd.org
Subject: Re: Unit number allocation API 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Oct 2004 05:11:36 -0000

In message: <48733.1096570677@critter.freebsd.dk>
            "Poul-Henning Kamp" <phk@phk.freebsd.dk> writes:
: My personal guess is that driver->attach() and driver->probe() will
: never get out from Giant (I can't seriously see the benefits as
: being bigger than the effort) and therefore I think the problem of
: locking API's like this can be wholesale ignored for a very long
: time.

This is my guess as well.  I have in my tree some locking assertions
to make sure this is the case, and hope to commit them soon.

Warner