On Sun, Oct 13, 2002, David Brownell <[EMAIL PROTECTED]> wrote: > > Once again, this is called bandwidth reservation. Reservation means to > > hold for one's use. It doesn't directly correlate to when it is actually > > used. You reserve a hotel room, for instance, before you use it. It's > > merely a guarantee for future usage. > > Linux drivers have so far shown no need to reserve bandwidth in advance. > They're working just fine on the "look for an interesting hotel and ask > for a room" strategy; room shortage hasn't been a problem in practice, > and there's only one rate after all.
In practice, this hasn't be a significant problem, but it's a race condition nonetheless and should be fixed. > That's not to say an API like that couldn't be done -- though it'd mean > more work for HCDs than the current approach, and would create many > opportunities for errors/bugs. (Like drivers that grab bandwidth and > never use it, starving out other drivers ... potentially quite nasty > to track down the culprit, especially given TTs.) Yes, bad drivers can screw up things, but they can do that in any number of ways. One way to track this down is to export the list of reserved bandwidth via driverfs. JE ------------------------------------------------------- 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
