From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB - prio and rate
Date: Fri, 02 Dec 2005 20:31:26 +0000 [thread overview]
Message-ID: <1133555489.20096.3.camel@pc.local> (raw)
In-Reply-To: <BF782D07436CAE4B931BFA5B2C68FF4F0F8E44@bmts1.ad.bmtseatech.co.uk>
[-- Attachment #1.1: Type: text/plain, Size: 997 bytes --]
On Fri, 2005-12-02 at 21:25 +0100, Andreas Klauer wrote:
> Actually, a class is always able to use it's rate at any time. The prio has
> only an effect when the class is trying to borrow bandwidth from others -
> then the high prio classes are allowed to take what they need first.
I have wondered about something like this too. I want to simply
prioritize my upstream bandwidth use, not limit it's use by anything.
Just say (for example) that if an SSH packet is somewhere in the
outbound direction when it hits the queue it gets put to the front of
the queue to minimize the latency of SSH whereas something like
bittorrent waits for SSH but otherwise gets full use of the upstream
bandwidth. In fact if I were to saturate the upstream with SSH,
something like bittorrent should effectively get no bandwidth at all.
I think this is what Mark wants to, if I'm understanding him correctly.
b.
--
My other computer is your Microsoft Windows server.
Brian J. Murrell
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-12-02 20:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 13:57 [LARTC] HTB - prio and rate Mark Lidstone
2005-12-02 20:25 ` Andreas Klauer
2005-12-02 20:31 ` Brian J. Murrell [this message]
2005-12-02 20:48 ` Andreas Klauer
2005-12-02 22:24 ` Brian J. Murrell
2005-12-03 6:04 ` Andreas Klauer
2005-12-03 23:14 ` Brian J. Murrell
2005-12-04 2:32 ` Jeffrey B. Ferland
2005-12-04 3:17 ` Jason Boxman
2005-12-04 3:26 ` Jason Boxman
2005-12-04 6:24 ` Andreas Klauer
2005-12-04 13:48 ` Brian J. Murrell
2005-12-04 15:14 ` Jeffrey B. Ferland
2005-12-04 16:05 ` Brian J. Murrell
2005-12-05 9:40 ` Mark Lidstone
2005-12-05 18:15 ` Andreas Klauer
2005-12-06 12:27 ` Mark Lidstone
2005-12-13 8:51 ` Mark Lidstone
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=1133555489.20096.3.camel@pc.local \
--to=brian@interlinx.bc.ca \
--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.