From: Andreas Klauer <Andreas.Klauer@metamorpher.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] (simplified) Rate precision
Date: Mon, 03 Nov 2003 00:37:26 +0000 [thread overview]
Message-ID: <marc-lartc-106782411004919@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106772021820294@msgid-missing>
Am Saturday 01 November 2003 21:32 schrieb Peteris Krumins:
> i wrote a few days ago but did not receive any answers.
I did not receive/read this mail.
> The example above should shape the speed to 2mbit (2048kbit)
> but unfortunately the real speed is only 1920kbit..
How exactly do you measure the 'real speed'? The difference sounds much like
overhead of some sort that you're not accounting properly. For example, when
using scp to copy files over the line, it would be normal to have lower
transfer rates than the actual line speed, because there's some kind of
handshake/encryption overhead with every package sent.
Regards,
Andreas Klauer
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-11-03 0:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-01 20:32 [LARTC] (simplified) Rate precision Peteris Krumins
2003-11-03 0:37 ` Andreas Klauer [this message]
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-106782411004919@msgid-missing \
--to=andreas.klauer@metamorpher.de \
--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.