Date: Thu, 20 Feb 2003 10:02:09 -0600 (CST) From: Mike Silbersack <silby@silby.com> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: Sam Leffler <sam@errno.com>, Scott Long <scott_long@btc.adaptec.com>, 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: <20030220100033.B2758@odysseus.silby.com> In-Reply-To: <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> <20030220093631.A48177@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 20 Feb 2003, Andrew Gallatin wrote: > 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 I noticed that as well when I took a look, so it does appear that bus_dmamem* may be useable with much locking. Still, someone should definitely review those routines and put in appropriate comments on locking requirements / etc. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030220100033.B2758>