Date: Wed, 19 Feb 2003 21:28:40 -0600 (CST) From: Mike Silbersack <silby@silby.com> To: 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: <20030219212343.O64167@patrocles.silby.com> In-Reply-To: <3E54219C.9030103@btc.adaptec.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>
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. > I've seen performance gains as high as 20%. Presumably this is because > you eliminate the two extra context switches that result from blocking > on Giant. I doubt that you'll see much gain in a UP system, but I > haven't benchmarked it. Once Peter commits his lazy context switching > patches, this gain won't be as dramatic anymore. > > Scott I suppose that I can always use the mutex profiling code to get a rough idea of how the situation changes as a result of locking. 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?20030219212343.O64167>