All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Leszek A. Szczepanowski" <twinsen@plusnet.pl>
To: lartc@vger.kernel.org
Subject: [LARTC] Conflict in designing HTB tree...
Date: Thu, 27 Feb 2003 21:52:28 +0000	[thread overview]
Message-ID: <marc-lartc-104638292118011@msgid-missing> (raw)

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/

             reply	other threads:[~2003-02-27 21:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-27 21:52 Leszek A. Szczepanowski [this message]
2003-02-28  8:08 ` [LARTC] Conflict in designing HTB tree Stef Coene

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-104638292118011@msgid-missing \
    --to=twinsen@plusnet.pl \
    --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.