From: Jason Boxman <jasonb@edseek.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB MPU
Date: Thu, 13 May 2004 21:59:36 +0000 [thread overview]
Message-ID: <200405131759.36895.jasonb@edseek.com> (raw)
In-Reply-To: <40A37E1B.8060604@dsl.pipex.com>
On Thursday 13 May 2004 13:28, Andreas Klauer wrote:
> Am Thursday 13 May 2004 16:38 schrieb Andreas Klauer:
> > Am Thursday 13 May 2004 15:54 schrieb Andy Furniss:
> > > I've just noticed that there is a patch on devik's site which does mpu
> > > and overhead.
> >
> > I'll give it a try. Thanks for the hint.
>
> Well, patching was a little difficult... it didn't like the debian patch
> and I didn't succeed in joining the two patches together because of the
> weird inject stuff. But anyway. It seems to work, and it looks useful, so
> I added it to the "Hacks" section of my Fair NAT script together with a
> patched binary.
Nifty.
But how do you determine what your minimum packet unit (MPU) is? How about
overhead for a PPPoE connection?
With shaping I can max my upstream and still maintain ~ 120ms ping times, but
I'd like to get it down to around ~ 70ms.
> Andreas
_______________________________________________
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-13 21:59 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 [this message]
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
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=200405131759.36895.jasonb@edseek.com \
--to=jasonb@edseek.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.