All of lore.kernel.org
 help / color / mirror / Atom feed
* [LARTC] Conflict in designing HTB tree...
@ 2003-02-27 21:52 Leszek A. Szczepanowski
  2003-02-28  8:08 ` Stef Coene
  0 siblings, 1 reply; 2+ messages in thread
From: Leszek A. Szczepanowski @ 2003-02-27 21:52 UTC (permalink / raw)
  To: lartc

I have 1024 Mbit link to Internet.
This link is shared by 3 LANs on my linux box.
And now - I have to design that these 3 LANs
gets some fragment of bandwidth. For example,
rates are: 128/384/512. Ceil is always at link speed.
I keep rule from FAQ on www.docum.org, which learn
us: sum of childs rates <= ceil of parent.
But if I define 3 classes based of customer conception
(paying for desired bandwidth), where is place for
creating some interactive classes for traffic like ICMP,
ACK responses and so on ? If I define next class, give it
highest priority, rate of 512 kbit, this exceeds rule from
FAQ, because 128+384+512+512 is not 1024 at all ;-)
So, how to resolve this kind of problem ? Or better I have
to change conception, and assume that I must create all kind
of classes (interactive, for big traffic and others) WITHIN
parent customer classes, on 'per customer' basis ?
This is not clear explained in manuals...
-- 
    Leszek A.      [The chance of a lifetime is passing you by.]
  Szczepanowski    [ Use it or lose it in the wink of an eye.  ]
twinsen@plusnet.pl [ Turn around, giving more than you take.   ]
    gg:275696      [       Lost and found in the past.         ]

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [LARTC] Conflict in designing HTB tree...
  2003-02-27 21:52 [LARTC] Conflict in designing HTB tree Leszek A. Szczepanowski
@ 2003-02-28  8:08 ` Stef Coene
  0 siblings, 0 replies; 2+ messages in thread
From: Stef Coene @ 2003-02-28  8:08 UTC (permalink / raw)
  To: lartc

On Thursday 27 February 2003 22:52, Leszek A. Szczepanowski wrote:
> I have 1024 Mbit link to Internet.
> This link is shared by 3 LANs on my linux box.
> And now - I have to design that these 3 LANs
> gets some fragment of bandwidth. For example,
> rates are: 128/384/512. Ceil is always at link speed.
> I keep rule from FAQ on www.docum.org, which learn
> us: sum of childs rates <= ceil of parent.
> But if I define 3 classes based of customer conception
> (paying for desired bandwidth), where is place for
> creating some interactive classes for traffic like ICMP,
> ACK responses and so on ? If I define next class, give it
> highest priority, rate of 512 kbit, this exceeds rule from
> FAQ, because 128+384+512+512 is not 1024 at all ;-)
You can do this.  But then it's possible that you are sending more data then 
your link can handle.  This is not problem, but it's possible that use some 
control over the bandwidth and that your latency goes up (modem queue will be 
filled).

> So, how to resolve this kind of problem ? Or better I have
> to change conception, and assume that I must create all kind
> of classes (interactive, for big traffic and others) WITHIN
> parent customer classes, on 'per customer' basis ?
Indeed.  You can create extra classes within the the customer class so you can 
give some packets a higher priority.

Stef

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2003-02-28  8:08 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-02-27 21:52 [LARTC] Conflict in designing HTB tree Leszek A. Szczepanowski
2003-02-28  8:08 ` Stef Coene

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.