Re: USB short packets and physical data packet length
- From: Mark McDougall <markm@xxxxxxxxx>
- Date: Fri, 04 Jul 2008 11:21:13 +1000
brad@xxxxxxxxxxx wrote:
In other words, if we define a bulk endpoint as 512-bytes, is it
wastefull of bandwidth if the endpoint is also used for transfers
that are all alwyas very much smaller than this maximum packet size?
Is it more bandwidth efficient to simply define a second endpoint with a smaller wMaxPacketSize?
IIUC, USB transfers are organised as transactions in a microframe. The USB host arbiter will allocate timeslots for transactions based on the pipe type, maximum packet size of each pipe and the availability of data.
So yes, IIUC a pipe with max=512 will always occupy a timeslot equivalent to a packet of 512 bytes, regardless of the number of bytes in the packet (not being familiar with the physical line protocol, I'm not sure you can say that it's "padded" at all, but this is completely irrelevant from a software POV).
The corollary is that a smaller *max* packet size will free up more of the microframe for other transfers.
That's my understanding - happy to be corrected.
Regards,
--
Mark McDougall, Engineer
Virtual Logic Pty Ltd, <http://www.vl.com.au>
21-25 King St, Rockdale, 2216
Ph: +612-9599-3255 Fax: +612-9599-3266
.
- Follow-Ups:
- Re: USB short packets and physical data packet length
- From: Peter Petersen
- Re: USB short packets and physical data packet length
- References:
- Prev by Date: USB short packets and physical data packet length
- Next by Date: Re: How workable is Vista?
- Previous by thread: USB short packets and physical data packet length
- Next by thread: Re: USB short packets and physical data packet length
- Index(es):
Relevant Pages
|