From: Ed Wildgoose <lists@wildgooses.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] patch: HTB update for ADSL users
Date: Mon, 21 Jun 2004 10:04:50 +0000 [thread overview]
Message-ID: <40D6B2C2.2050300@wildgooses.com> (raw)
In-Reply-To: <40D2D5CB.2000804@wildgooses.com>
>So does it just let you be honest about your rated speed, or is there an added
>performance bonus from being able to specify your true ATM rate?
>
>
The idea is that your ethernet packets get broken up and encapsulated in
53 byte ATM packets. Each ATM packet is fixed size and has a 5 byte
header = 48 bytes of data.
Straight off that means that the 512Kbit bandwidth you bought is only
good for 512/53 * 48 = 463 Kbit or 58 Kbytes/s. However, unless your
packets are exactly a multiple of 48 then you will be wasting bandwidth
big time (think about your MTU). Consider small ack packets which will
take up two cells, but the second cell is basically empty (bandwidth
slashed in half). Unless all your packets are the same size, this is
why the current mutliply by some fixed constant approach is not working
perfectly with ADSL.
So the patch simply works out how many cells you will need and
multiplies up by the real size of those cells to work out bw used.
It's also more conservative than before. Previously it was working out
an effective rate for 8 byte packets, and using that rate for 8-15 byte
packets. Now it works out the rate for 15 byte packets and uses *that*
for 8-15 byte packets.
It's probably not perfect, but it's extremely accurate for me. I can
bump up the bandwidth on my interfaces to basically 99% and for stable
streams there is no queuing. P2P still seems to cause so many new
incoming connections that you need to throttle down the incoming to
leave some space for an unexpected incoming rush - but for most users I
think it will work nicely
Ed W
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-06-21 10:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-18 11:45 [LARTC] patch: HTB update for ADSL users Ed Wildgoose
2004-06-18 21:43 ` Andy Furniss
2004-06-18 23:00 ` Ed Wildgoose
2004-06-19 0:33 ` Andy Furniss
2004-06-19 12:29 ` Ed Wildgoose
2004-06-19 12:54 ` syrius.ml
2004-06-19 13:40 ` Ed Wildgoose
2004-06-20 7:27 ` Jason Boxman
2004-06-20 12:31 ` Andy Furniss
2004-06-20 13:16 ` Ed Wildgoose
2004-06-20 16:46 ` Ed Wildgoose
2004-06-20 17:10 ` Ed Wildgoose
2004-06-21 6:08 ` Jason Boxman
2004-06-21 10:04 ` Ed Wildgoose [this message]
2004-06-22 0:38 ` Damion de Soto
2004-06-22 5:15 ` Jason Boxman
2004-06-22 9:54 ` Ed Wildgoose
2004-06-22 10:00 ` Ed Wildgoose
2004-06-22 17:16 ` Jason Boxman
2004-06-22 21:52 ` Jason Boxman
2004-06-23 12:52 ` ThE LinuX_KiD
2004-06-23 14:00 ` Ed Wildgoose
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40D6B2C2.2050300@wildgooses.com \
--to=lists@wildgooses.com \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.