From: "Aron Brand" <Aron@sofaware.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Controlling only delay using HTB without stealing excess bandwidth
Date: Mon, 15 Dec 2003 17:18:59 +0000 [thread overview]
Message-ID: <marc-lartc-107150892502992@msgid-missing> (raw)
Hi Gurus,
The documentation isn't terribly clear, but it seems that the HTB 'prio'
field has two separate functions:
1. Classes with lower prio get all the excess bandwidth first.
2. Classes with lower prio get lower delay.
I want just #2 - and not #1
In other words, for example lets say that I have a 100kbps link, divided
to classes A and B as following.
A - rate kbps limit\x100kbps
B - rate kbps limit\x100kbps
How can I get class B to have a lower delay than A, while still sharing
the excess bandwidth fairly with A?
Thanks,
Aron Brand
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-12-15 17:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-15 17:18 Aron Brand [this message]
2003-12-15 18:14 ` [LARTC] Controlling only delay using HTB without stealing excess bandwidth Roy
2003-12-15 19:09 ` Mike
2003-12-16 7:53 ` [LARTC] Controlling only delay using HTB without stealing Cezar Atanasiu
2003-12-16 13:31 ` [LARTC] Controlling only delay using HTB without stealing excess bandwidth Roy
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-107150892502992@msgid-missing \
--to=aron@sofaware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox