Date: Wed, 19 Feb 2003 20:01:46 -0800 From: "Sam Leffler" <sam@errno.com> To: "Mike Silbersack" <silby@silby.com>, "Scott Long" <scott_long@btc.adaptec.com> Cc: "Andrew Gallatin" <gallatin@cs.duke.edu>, <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: <0d1a01c2d894$c99c0540$52557f42@errno.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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-src" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0d1a01c2d894$c99c0540$52557f42>