> Yes, because the HCD may need to allocate space from its private pools
> based on the total length of the URB's transfer buffer.
>
> It's unclear to me to what extent all these things really need to be
> allocated beforehand, however. Certainly for things like usb-storage it
> makes sense to do this with buffers involved in actual data transfers, to
> minimize latency if nothing else. But for subsidiary usages, like the
> URBs and buffers used in doing a reset? These are pretty rare and not
> especially time-critical, although they do need to use GFP_NOIO.
We want only one method of URB allocation, don't we?
> > It would have more benefits, even
> > in unlikely places like usb_kill_urb().
>
> I'm puzzled how pre-allocation would help usb_kill_urb().
Reentrancy. The URB can be resubmitted from the completion handler, but
it cannot have completed.
> > Yet it is a major rewrite and we decided that it's 2.7 matter.
>
> It's one of the items on the slate -- but note that the Gadget API does
> this already.
To its credit and benefit.
Regards
Oliver
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
