From: Ed Wildgoose <lists@wildgooses.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB MPU
Date: Mon, 24 May 2004 23:42:56 +0000 [thread overview]
Message-ID: <40B28880.5080502@wildgooses.com> (raw)
In-Reply-To: <40A37E1B.8060604@dsl.pipex.com>
Jason Boxman wrote:
>On Friday 14 May 2004 03:05, Ed Wildgoose wrote:
><snip>
>
>
>>I appears that you could change the patch in tc/core in fn
>>tc_calc_rtable, from:
>>
>> + if (overhead)
>> + sz += overhead;
>>
>>to something like:
>>
>> + if (overhead)
>> + sz += (((sz-1)/mpu)+1) * overhead;
>>
>>
>
>I did that and recompiled iproute2. I kicked my rate up to my actual
>connection, 256Kbps, and I was nailed as usual. No measurable change using
>the above with an mpu of 54 for each class. Nothing changed at my
>handicapped rate of 160kbit either.
>
>
>
I think that calculation needs to be changed so that the divisor "mpu"
should become 48, and the overhead will be 5
You could change the whole size calculation to be this instead (ie no IF):
sz = ( (int)((sz-1)/48) + 1) * 53;
Note I don't have the code in front of me, so you may need to tweak that
a bit. The idea though is that you get 48 data bytes in each ATM cell,
hence we work out how many cells are required. Then we multiply by 53
which is that actual size of the atm cell. Clear as mud?
>What would be nice is something that would calculate the actual PPPo(E|A)
>overhead on the fly at runtime and schedule accordingly.
>
>
That's what it ought to do...
Please try this alteration and see if it works any better. (Note: I
think that MPU will need to be 48 for the purposes of this code? Check
my logic, but setting it to 48 is a little low, but the above
calculation will then kick in and change it to 53 which is your real min
packet size. Otherwise we will double count.
Interested to hear if this works...
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-05-24 23:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-13 13:54 [LARTC] HTB MPU Andy Furniss
2004-05-13 14:38 ` Andreas Klauer
2004-05-13 17:28 ` Andreas Klauer
2004-05-13 21:59 ` Jason Boxman
2004-05-14 7:05 ` Ed Wildgoose
2004-05-14 8:40 ` Andy Furniss
2004-05-14 9:55 ` Andy Furniss
2004-05-14 17:10 ` Jason Boxman
2004-05-17 22:36 ` Andy Furniss
2004-05-17 23:33 ` Andy Furniss
2004-05-20 6:29 ` Jason Boxman
2004-05-20 11:13 ` Andy Furniss
2004-05-21 8:19 ` syrius.ml
2004-05-24 20:53 ` Jason Boxman
2004-05-24 23:42 ` Ed Wildgoose [this message]
2004-05-28 18:54 ` Andy Furniss
2004-05-28 19:18 ` Jason Boxman
2004-05-28 21:49 ` Ed Wildgoose
2004-05-30 7:40 ` Andy Furniss
2004-05-30 7:49 ` Andy Furniss
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=40B28880.5080502@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.