From owner-cvs-src Thu Feb 20 8:22: 9 2003 Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BD81937B401; Thu, 20 Feb 2003 08:22:06 -0800 (PST) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAD2543F85; Thu, 20 Feb 2003 08:22:05 -0800 (PST) (envelope-from sam@errno.com) Received: from melange (melange.errno.com [66.127.85.82]) (authenticated bits=0) by ebb.errno.com (8.12.5/8.12.1) with ESMTP id h1KGM2nN046342 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Thu, 20 Feb 2003 08:22:02 -0800 (PST)?g (envelope-from sam@errno.com)œ X-Authentication-Warning: ebb.errno.com: Host melange.errno.com [66.127.85.82] claimed to be melange Message-ID: <0dcd01c2d8fc$33a49ee0$52557f42@errno.com> From: "Sam Leffler" To: "Andrew Gallatin" Cc: "Mike Silbersack" , "Scott Long" , , , 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> <20030220093631.A48177@grasshopper.cs.duke.edu> Subject: Re: cvs commit: src/sys/dev/aac aac.c aac_pci.c Date: Thu, 20 Feb 2003 08:22:02 -0800 Organization: Errno Consulting MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-cvs-src@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. Correct, for nic drivers you either pre-allocator or you map data associated with mbufs (or private store if you do jumbograms and set them up as externally-managed storage). In general though, unless you pre-allocate memory you may need to use it at the point where you setup for dma. The ubsec crypto driver currently uses it when handling asymmetric crypto ops. Sam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-src" in the body of the message