Workaround for USB DMA bugs

David Gibson david at
Thu Apr 4 15:23:49 EST 2002

On Wed, Apr 03, 2002 at 11:09:04PM -0500, Dan Malek wrote:
> David Gibson wrote:
> >Oh, right, yes.  That was actually what I was meaning when I said
> >"aligned" (sort of aligned at both ends), forgetting that the normal
> >meaning only applies to the start address.
> I guess if we can ensure a DMA-only pool, simple alignment will work.
> You just can't kmalloc() because you don't know what may follow something
> that isn't modulo cache line size.  You also have to be careful of code
> that allocates a large object, then uses part of it for DMA and other
> parts for processor core data.  I'm not sure we want to require kmalloc()
> to always cache align due to the potential for wasted memory space.

kmalloc() already guarantess cacheline alignment (at the beginning).
Which means it is safe as long as the allocation is a multiple of the
cacheline size (which comes for free on allocations of a largish power
of 2, a common case).

Possibly a better approach would be to make the consistent_sync()
function be more careful and flush rather than invalidate cachelines
which are only partially covered by the region given.  At the moment
it invalidates everything and hence is only safe for regions which are
cacheline aligned, and of size a multiple of cacheline size.

David Gibson			| For every complex problem there is a
david at	| solution which is simple, neat and
				| wrong.  -- H.L. Mencken

** Sent via the linuxppc-embedded mail list. See

More information about the Linuxppc-embedded mailing list