True. However, the first problem of guaranteed throughput is that nobod=
y
else is grabbing more bandwidth than available. Your patch will allow m=
e to
route everything else (on the local host...) through a limiter or two,
thereby solving _that_ problem.
Thus, _if_ everything else works out right, then we get something
resembling guaranteed throughput with what you're doing. Guaranteeing t=
hat
all these other things indeed do work out right is the next problem. ;=
-)
> Firstly its a soft realtime problem, secondly its a tricky resource
> management problem and thirdly you can't do it on a shared network bu=
s
> (eg ethernet).
>=20
All too true... but there are enough cases out there where all of this
isn't really a problem.
--=20
Dime is money.
--=20
Matthias Urlichs \ noris network GmbH / Xlink-POP N=FCrnberg=
=20
Schleiermacherstra=DFe 12 \ Linux+Internet / EMail: urlichs@nor=
is.de
90491 N=FCrnberg (Germany) \ Consulting+Programming+Networking+etc=
'ing
PGP: 1024/4F578875 1B 89 E2 1C 43 EA 80 44 15 D2 29 CF C6 C7 E0 D=
E
Click <A HREF=3D"http://info.noris.de/~smurf/finger">here</A>. =
42