From owner-cvs-all Wed Feb 19 20: 1:54 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 F237F37B401; Wed, 19 Feb 2003 20:01:52 -0800 (PST) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id DAF2143F85; Wed, 19 Feb 2003 20:01:51 -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 h1K41knN043985 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Wed, 19 Feb 2003 20:01:46 -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: <0d1a01c2d894$c99c0540$52557f42@errno.com> From: "Sam Leffler" To: "Mike Silbersack" , "Scott Long" Cc: "Andrew Gallatin" , , , 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> Subject: Re: cvs commit: src/sys/dev/aac aac.c aac_pci.c Date: Wed, 19 Feb 2003 20:01:46 -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-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > 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. Sam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message