Date: Fri, 15 Nov 2002 09:50:28 -0800 From: Chuck Tuffli <chuck_tuffli@agilent.com> To: mark tinguely <tinguely@web.cs.ndsu.nodak.edu> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: bus_dmamem_alloc failing Message-ID: <20021115175028.GC19814@cre85086tuf.rose.agilent.com> In-Reply-To: <200211151703.gAFH3ij16483@web.cs.ndsu.nodak.edu> References: <20021115164813.GB19814@cre85086tuf.rose.agilent.com> <200211151703.gAFH3ij16483@web.cs.ndsu.nodak.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Nov 15, 2002 at 11:03:44AM -0600, mark tinguely wrote: [snip] > The memory is avaliable to the kernel/drivers when bus_dmamem_free() is > called. The problem for you is that someone else does allocate a > page within the 16 page chunk making it unable to reallocatable by you, > so the next bus_dmamem_alloc() looks for the next 16 page contiguous > chunk. This continues until there is no more 16 page contiguous chunks > available and the bus_dmamem_alloc() fails. FreeBSD does not have a > physical memory defragmenter. Ok, I get it now. Thanks to all for the explanation. Would a physical defragmenter be of interest? I can't work on it right away, but if there is interest, I could take a look at this later. -- Chuck Tuffli <chuck_tuffli AT NO_SPAM agilent DOT com> Agilent Technologies, Storage and Networking To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021115175028.GC19814>