From: Ed Wildgoose <lists@wildgooses.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] patch: HTB update for ADSL users
Date: Tue, 22 Jun 2004 10:00:48 +0000 [thread overview]
Message-ID: <40D80350.40805@wildgooses.com> (raw)
In-Reply-To: <40D2D5CB.2000804@wildgooses.com>
>I'm running PPPoEoATM here. I don't know what my actual PPPoE overhead is,
>but I guess 10 bytes is reasonably close enough. PPPoE is handled by my
>Westell Wirespeed, which doesn't provide any useful cell information. At the
>moment I cannot easily obtain a cell count to determine my actual PPP
>overhead.
>
>
Try bumping the protocol_overhead up to 16 for PPPoE (from 10). You
should also make sure that your MTU is lower than that required by your
PPPoE provider or else you will get ethernet packet fragmentation and I
doubt we want to extend the patch to cover those situations anyway.
The patch should actually have most benefit when you are doing transfers
with smaller packets. I think with larger constant streams like the one
you tested, there will be little difference between bumping up the
interface speed with the patch or leaving it all as it was (at the end
of the day we are mostly just shifting the calculation of interface
speed somewhere else).
>Perhaps I need to idle everything and do one of those 'speed tests' to see
>what my actual upstream is. Could be it's really around 224, since I'm not
>guaranteed 256 by my ISP anyway.
>
>
Your upstream will be 256Kbits of ATM bandwidth. This consists of 53
byte packets with 48 bytes of data. So you already only have 256 *
48/53 of real bandwidth. We then have to take off PPP headers and PPPoE
headers.
We are obviously still a few bytes out with this patch or else you
should be able to crank up the speed to 250 ish and still see your ping
speeds stay low. I will investigate further
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-22 10:00 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
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 [this message]
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=40D80350.40805@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.