Hi,
It's not for a particular use that I was asking, it was just for my
understanding.
So what I think people are saying is:
1) The sum of all HTB classes under a single HTB qdisc should
add up to the maximum rate of the qdisc
2) HTB's prio is only used when 'borrowing' bandwidth from other
classes under the same HTB qdisc, then classes with a given prio will
only be able to "borrow" bandwidth when classes with a lower prio have
nothing waiting
Is this correct?
Many thanks,
Mark Lidstone
IT and Network Support Administrator
BMT SeaTech Ltd
Grove House, Meridians Cross, 7 Ocean Way
Ocean Village, Southampton. SO14 3TJ. UK
Tel: +44 (0)23 8063 5122
Fax: +44 (0)23 8063 5144
E-Mail: mailto:[EMAIL PROTECTED]
Website: www.bmtseatech.co.uk
========================================================================
==
Confidentiality Notice and Disclaimer:
The contents of this e-mail and any attachments are intended only for
the
use of the e-mail addressee(s) shown. If you are not that person, or one
of those persons, you are not allowed to take any action based upon it
or
to copy it, forward, distribute or disclose the contents of it and you
should please delete it from your system. BMT SeaTech Limited does not
accept liability for any errors or omissions in the context of this
e-mail
or its attachments which arise as a result of Internet transmission, nor
accept liability for statements which are those of the author and not
clearly made on behalf of BMT SeaTech Limited.
========================================================================
==
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brian J. Murrell
Sent: 02 December 2005 20:31
To: [email protected]
Subject: Re: [LARTC] HTB - prio and rate
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
_______________________________________________
LARTC mailing list
[email protected]
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
