Oliver Neukum wrote:
> 
> Am Sonntag, 10. November 2002 06:45 schrieb Randy.Dunlap:
> > David Brownell wrote:
> >
> >
> > ...
> >
> > > Your stack trace showed usblp_check_status() was what started this
> > > sequence of troubles, so I looked at it.  There were some issues,
> > > it's got a lot of pretty early usb code:
> > >
> > >   - it assumes it's OK to DMA onto the stack.  kmalloc would likely
> > >     be the best fix.
> >
> > Patch for this is attached.  Please apply.
> 
> If you do this, you should allocate the buffers seperately, because
> only then are you sure that there are no DMA issues.

OK, I was planning to redo it anyway to allocate them
separately to reduce allocation wastage (8 KB + 8 KB + 8 bytes
doesn't allocate into a slab very nicely I think).

So Greg, just drop that one and I'll prepare another one.

Oliver, what kind of DMA issues are you referring to?
IOW is it a problem that the read and write buffers are
allocated together?  (that is, if the read buffer were being
used, which I suspect is rare)

~Randy


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to