From owner-freebsd-arch@FreeBSD.ORG Tue Aug 1 12:21:55 2006 Return-Path: X-Original-To: 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 5D4B716A4DD; Tue, 1 Aug 2006 12:21:55 +0000 (UTC) (envelope-from gallatin@cs.duke.edu) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id DCE3C43D69; Tue, 1 Aug 2006 12:21:54 +0000 (GMT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.13.6/8.13.6) with ESMTP id k71CLnCd024908 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 1 Aug 2006 08:21:49 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id k71CLixZ060991; Tue, 1 Aug 2006 08:21:44 -0400 (EDT) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17615.18264.172863.892776@grasshopper.cs.duke.edu> Date: Tue, 1 Aug 2006 08:21:44 -0400 (EDT) To: Robert Watson In-Reply-To: <20060731105045.X16341@fledge.watson.org> References: <20060730141642.D16341@fledge.watson.org> <44CCFC2C.20402@errno.com> <20060730200929.J16341@fledge.watson.org> <200607311024.50537.hselasky@c2i.net> <20060731105045.X16341@fledge.watson.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Cc: arch@FreeBSD.org, net@FreeBSD.org, freebsd-arch@FreeBSD.org, Hans Petter Selasky Subject: Re: Changes in the network interface queueing handoff model X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Aug 2006 12:21:55 -0000 Robert Watson writes: > tear-down magic. What Solaris does here, FYI, is basically add a lock around > entering the device driver via their mac layer in order to prevent it from > "disappearing" while in use via the ifnet interface. I'm not sure if we want At least for GLDv2, this is a reader-writer lock. The transmit and receive paths take a read lock on the device's macinfo (like ifnet) struct, and the detach code takes a write lock. The Solaris driver model does not serialize transmits (or receives), as one might think from reading the above. Drew