From owner-cvs-all Thu Feb 20 6:36:43 2003 Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CBE7637B401; Thu, 20 Feb 2003 06:36:41 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id EFA4B43F3F; Thu, 20 Feb 2003 06:36:40 -0800 (PST) (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.12.6/8.12.6) with ESMTP id h1KEab8I027173 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 20 Feb 2003 09:36:37 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id h1KEaWd48198; Thu, 20 Feb 2003 09:36:32 -0500 (EST) (envelope-from gallatin@cs.duke.edu) Date: Thu, 20 Feb 2003 09:36:32 -0500 From: Andrew Gallatin To: Sam Leffler Cc: Mike Silbersack , Scott Long , src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/aac aac.c aac_pci.c Message-ID: <20030220093631.A48177@grasshopper.cs.duke.edu> References: <200302192158.h1JLwYJn025529@repoman.freebsd.org> <20030219161458.T62705@patrocles.silby.com> <20030219181629.A46948@grasshopper.cs.duke.edu> <20030219182122.N62705@patrocles.silby.com> <3E54219C.9030103@btc.adaptec.com> <20030219212343.O64167@patrocles.silby.com> <0d1a01c2d894$c99c0540$52557f42@errno.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <0d1a01c2d894$c99c0540$52557f42@errno.com>; from sam@errno.com on Wed, Feb 19, 2003 at 08:01:46PM -0800 X-Operating-System: FreeBSD 4.4-RELEASE on an i386 Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sam Leffler [sam@errno.com] wrote: > > On Wed, 19 Feb 2003, Scott Long wrote: > > > > > busdma has been around since 3.0. It probably needs a couple of hours > > > of work to lock it down. > > > > Hm, icky. Is anyone in the know wrt busdma looking into handling that? I > > don't think we can get much done in the network drivers without touching > > busdma functions. > > > > Since most bus_dma functions operate on driver-private data locking drivers > will probably be sufficient to start. The only issue I know of is that > bus_dmamem_alloc calls contigmalloc; so there may be an issue there getting > out from under Giant. > I'm not the most familiar person with the busdma interface.. but.. at least for network drivers, bus_dmamem_alloc() is typically called for descriptor lists, etc. Eg, data shared with the nic, and is done at attach time, right? Its never called from the transmit or recv routines. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message