* explaining the math behind the buffering done in USB network drivers
@ 2012-11-08 17:35 Oliver Neukum
0 siblings, 0 replies; only message in thread
From: Oliver Neukum @ 2012-11-08 17:35 UTC (permalink / raw)
To: Robert Bradley, Dave Taht, Jim Gettys, netdev
Hi,
it is probably necessary to state the limitations of USB to understand
why we buffer as much data as we buffer. Basically the schedule on
the USB bus is set in stone for a period of 1ms(full speed). This means that a driver
has to have submitted to USB core enough data to fill _2_ such periods
at all times. Thus the schedule for the current period is filled up and the
host controller can seamlessly switch to the next period.
In addition the driver has to be ready to provide the data for the next period
as soon as one period is done.
Thus conceptually for USB we do tripple-buffering.
Few drivers actually express this logic internally. One usually calculates
a rough approximation, but this is the logic behind the thing.
Regards
Oliver
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2012-11-08 17:35 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-11-08 17:35 explaining the math behind the buffering done in USB network drivers Oliver Neukum
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox