From: Martin Devera <devik@cdi.cz>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] exploring HTB
Date: Fri, 15 Feb 2002 12:01:13 +0000 [thread overview]
Message-ID: <marc-lartc-101377456517863@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101361106601378@msgid-missing>
> > the slots was removed from latest code and link above is obsolete (where
> > you have found it ?) ;)
> I can still find this link despite of refreshing page in my browser, May
> some cache server running in between.
No cache .. the page is still on my server but it is treated
as obsolete. I just marked the link to it as such ;)
> COOL IMQ. How much throughput will be reduced or latency will be added
> while using IMQ? As in every flow it adds/increase one hope internally?
Yes it is one enqueue and dequeue for qdisc. So that is will add
latency as dictated by the qdisc .. So that there should be only
negligible unwanted performance hit.
> > Just to note that speed depends ONLY on number of ACTIVE classes (active
> > flows). Those without data enqueued are idle and don't decrease
> > throughtput.
> Presently I'm running setup with 200 queues (200 RED leaves and 200 u32
> classifiers), Thus basically a seperate queue for every individual in my
> organization. Ya I never knew about the dependency of throughput on active
> flows. I'm planing to go for 400 queues. Sometime before Documentations on
> Devik's home page stat that RED is not going to work with HTB and will
> simply eat CPU cycles. I couldn't locate it now anywhere? Does it works with
> new release of HTB?
I can't remember that I would have such note on my pages. But basically
HTB,CBQ and TBF are exclusive options. They don't fit well one into
another. It is because they are all absolute rate dependent and all are
non-work conserving.
RED is also dependant on absolute rate but it is work-conserving. So that
it can be used as CBQ's or HTB's leaf and there should be ho hard problem
with it. However I don't know RED sources well so that I can't predict
some obscure problems.
> > Also limiting is packet rate not byte rate .. The limit is somewhere
> But ultimately its going to limit on byte transfer, isn't it?
Yes as end effect it is.
devik
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
next prev parent reply other threads:[~2002-02-15 12:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-13 14:54 [LARTC] exploring HTB Sumit Pandya
2002-02-13 15:05 ` Stef Coene
2002-02-14 10:59 ` Martin Devera
2002-02-15 9:22 ` Sumit Pandya
2002-02-15 12:01 ` Martin Devera [this message]
2002-02-16 20:22 ` Don Cohen
2002-02-16 21:19 ` Martin Devera
2002-02-16 21:33 ` Don Cohen
2002-02-16 21:42 ` Martin Devera
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-101377456517863@msgid-missing \
--to=devik@cdi.cz \
--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.