From: Dancer Vesperman <dancer@anthill.echidna.id.au>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] newbie - shaping a PSTN connection
Date: Wed, 10 Sep 2003 00:43:49 +0000 [thread overview]
Message-ID: <marc-lartc-106315468902959@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106309566532407@msgid-missing>
No worries. Why does it work?
Every packet leaving an interface is up to MTU bytes in length. Let's
say that a byte is ten bits (8+ 1start+1stop). So a 1500byte packet is
15000 bits. On a 28.8K connection, that means a 1500 byte packet takes
0.52 seconds to transmit. Assuming that the queueing discipline is FIFO
(first-in-first out) and the queue length on the interface is, say, 10
packets, a packet can take 10*0.52 seconds to get to the head of the
queue. Plus transmission time, that's 5.2 (for queuing) +0.52 for
transmission. Quite a delay.
You may be able to do better by shortening the packet queue on the
interface (ip link set ppp0 qlen 4) for example. Or attaching an SFQ
queueing discipline (tc qdisc add dev ppp0 root handle 1: sfq perturb
10) - although for SFQ, I think you'd want a more substantive queue
length.
On Tue, 2003-09-09 at 18:52, Daniel Horth wrote:
> wow - from 8 second ping responses on my heavily loaded link to 2 second
> just by changing the MTU - sure I'll be able to improve further on that with
> experimentation.
>
> thanks for that!
>
> - dan.
>
>
> -----Original Message-----
> From: Dancer Vesperman [mailto:dancer@anthill.echidna.id.au]
> Sent: Tuesday, 9 September 2003 6:37 PM
> To: Daniel Horth
> Subject: Re: [LARTC] newbie - shaping a PSTN connection
>
>
> I'd seriously advise cutting your MTU/MRU down. A lot. Say as low as 562
> or 168. If your MTU/MRU is defaulting to 1500, it's going to be hard to
> get any effective shaping on your link.
>
> On Tue, 2003-09-09 at 18:21, Daniel Horth wrote:
> > Hi - I've been going through the LARTC how-to and have successfully used
> the
> > sample scripts (and wondershaper) with my xDSL links.
>
> __________________________________
> Euroluce Lighting Australia PTY LTD
> 92-94 Tennyson Road, Mortlake, NSW 2137
> Ph: (02) 9743 6099 Fx: (02) 9743 6406
> http://www.euroluce.com.au/
>
> The contents of this email are confidential. If you are not, or believe you
> may not be, the intended recipient of this email, please let us know by
> reply and then delete it from your system. You should not copy the message
> or disclose its contents to anyone. No warranty or other assurance is given
> by us that this email is free of any virus or any other defect or error.
>
> Any views or opinions presented in this email are solely those of the author
> and do not necessarily represent those of the company. If verification is
> required please request a hard-copy version.
>
> Scanned by Inflex - Queries to: postmaster@euroluce.com.au
--
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-09-10 0:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 8:21 [LARTC] newbie - shaping a PSTN connection Daniel Horth
2003-09-09 23:44 ` Damion de Soto
2003-09-10 0:43 ` Dancer Vesperman [this message]
2003-09-10 2:08 ` Dan Horth
2003-09-10 17:06 ` Stef Coene
2003-09-10 17:39 ` Stef Coene
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=marc-lartc-106315468902959@msgid-missing \
--to=dancer@anthill.echidna.id.au \
--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.