On Mon, 13 Mar 2000, [ISO-8859-1] Pawe� Krawczyk wrote:
> In article <001c01bf8c6a$cd16aaa0$0c03a8c0@sulem> you wrote:
>
> > I have just started playing around with QoS and am especially
> interested in u32. Please could someone suggest where I can find
> documenation on u32, or, explain how hashtables work and why they
> are used.
>
> AFAIK there's no documentation in English for U32, which is sad because
> it's really a great filter when you become familiar with it. Actually
> it would be great to see U32 in firewalling code, where it would beat
> ipchains and netfilter with no doubt ;) You can take a look at my
> article [1] in Polish about QoS in Linux, which contains a quite complete
> section on U32. There are some examples and table of parameters, that
> I've digged out from the source code - at least these two can be useful
> for you until I write new, English version of the article (which I've
> been planning for some time). Of course, if you can't read Polish :)
Don't read Polish, but in looking through the paper, and then
tc_util.c I found somthing interesting.
It appears kilo = *1024, mega = *1024*1024
How does this fit in with line rates? Datacom lines are not
powers of 2, a 100Mbit ethernet is not 100*1024*1024, it is
100*1000*1000, One-hundred million bits per second.
Also, the labels are confusing,
What are the input specs? bits or bytes? It looks like tc is treating
bps as bytes per secong and xbit as bits per second???
the input 100Mbit appears to give 13,107,200? Assuming bps = bytes
per second this is still wrong for a 100Mbit ethernet, 12,500,000
would be the correct figure.
Some one clue me in here. :)
---
As folks might have suspected, not much survives except roaches,
and they don't carry large enough packets fast enough...
--About the Internet and nuclear war.
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
