From: Abraham van der Merwe <abz@frogfoot.net>
To: lartc@vger.kernel.org
Subject: [LARTC] ESFQ - optimal parameters?
Date: Mon, 03 Feb 2003 15:23:22 +0000 [thread overview]
Message-ID: <marc-lartc-104428594504861@msgid-missing> (raw)
[-- Attachment #1: Type: text/plain, Size: 705 bytes --]
Hi!
Have anyone experimented with ESFQ yet? I'd like to know what the optimal
depth/divisor/perturb settings are for X kilobits/per/second.
For example, once could calculate the optimal limit parameter (bitrate (bps) *
latency / (mtu * 1000)), but what should depth/divisor be?
Also, what is the optimal perturb value in general for SFQ / ESFQ?
--
Regards
Abraham
There are times when truth is stranger than fiction and lunch time is one
of them.
___________________________________________________
Abraham vd Merwe [ZR1BBQ] - Frogfoot Networks
P.O. Box 3472, Matieland, Stellenbosch, 7602
Cell: +27 82 565 4451 Http: http://www.frogfoot.net/
Email: abz@frogfoot.net
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
reply other threads:[~2003-02-03 15:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-104428594504861@msgid-missing \
--to=abz@frogfoot.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox