All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] ADSL Calculator
Date: Thu, 16 Jun 2005 14:21:40 +0000	[thread overview]
Message-ID: <42B18AF4.5060703@dsl.pipex.com> (raw)
In-Reply-To: <20050614220232.GA17110@yamamaya.is-a-geek.org>

Andy Furniss wrote:
> Tobias Diedrich wrote:
> 
>> Hi,
>>
>> I've written a small javascript ADSL throughput calculator:
>> http://nukunuku.yamamaya.is-a-geek.org/~ranma/adsl.html
>>
>> Feel free to submit alternative presets (I currently have presets
>> for three german telecom speed variants: T-DSL (1000|2000|3000),
>> derived from
>> http://www2.lancom.de/kb.nsf/5d445c701b3ff52dc1256e7700297e5c/27c6ee1c3e3f74b0c1256e94004a433e?OpenDocument). 
>>
>>
>> Comments, suggestions, spelling nitpicks?
>>
> 
> Looks good - one picky point - if your overhead means only 4 bytes 
> padding at default mtu are needed, then reducing mtu to be "optimal" for 
> IP and above levels may be less efficient from the point of view of the 
> tcp data because of the reduced payload vs fixed overheads.
> 
> I haven't done the maths on that :-)

Which I should have done first :-)

If timestamps are off it's still about 1 1/3 bytes per frame more 
efficient. If they are on (default on linux costing 12 bytes) the 
smaller mtu is about 1 byte per frame less efficient.

Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2005-06-16 14:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-14 22:02 [LARTC] ADSL Calculator Tobias Diedrich
2005-06-16  1:01 ` Andy Furniss
2005-06-16 14:21 ` Andy Furniss [this message]
2005-06-16 15:25 ` Per Marker Mortensen

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=42B18AF4.5060703@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.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.