On Mon, 26 Dec 2005, Bodo Eggert wrote:
> On Mon, 26 Dec 2005, Lee Revell wrote:
> > On Mon, 2005-12-26 at 11:25 +0100, Bodo Eggert wrote:
>
> > > Document the current status of CONFIG_USB_BANDWITH implementation.
> >
> > Since most systems use uhci-hcd and/or ehci-hcd maybe we should just
> > mark it BROKEN? Or EXPERIMENTAL?
>
> It is EXPERIMENTAL, but the current documentation sounds like "YOU REALLY
> WANT THIS !!!1", and I /guess/ that would be true for ohci-hcd users.
CONFIG_USB_BANDWIDTH isn't _really_ needed. What it does (or rather, what
it would do if it worked properly) is prevent the kernel from
overcommitting on USB bandwidth.
If it's not set, the kernel will allow drivers to reserve more bandwidth
than is actually available, with the result that data transfers will fail.
If it is set, drivers will not be allowed to reserve too much bandwidth,
so again the I/O will fail (but at an earlier stage).
Provided drivers never try to overcommit, it doesn't matter whether the
option is set or not. And note that a single driver is most unlikely to
overcommit on bandwidth; the problems arise when you have more than one
driver all trying to use a lot of bandwidth at the same time.
Alan Stern
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
