All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sumit Pandya" <sumit@elitecore.com>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] exploring HTB
Date: Fri, 15 Feb 2002 09:22:14 +0000	[thread overview]
Message-ID: <marc-lartc-101377301614886@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101361106601378@msgid-missing>

-----Original Message-----
From: Martin Devera [mailto:devik@cdi.cz]

>> 3> A Small but nice document about Cross device sharing on link
>> http://luxik.cdi.cz/~devik/qos/htb/htbmeas1.htm. Can?t this limitation of
>> slot be increased?

> 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.

>The IMQ device is superior for Cross device sharing and it is a LOT simpler
;)
> See http://luxik.cdi.cz/~devik/qos/
	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?

>> 4> It would be nice if someone help me by providing statistics over
number
>> of queues and filter. What is maximum limit of these two for a PIII 700
with
>> 256 MB RAM? How much maximum bandwidth can be shaped?

> I've tried on my pII 375, I was able to shape 100Mbit with 5 classes (3
> leaves). But both CBQ and HTB has O(N) worst case complexity where N is
> no of classes. I just finished new HTB design (with the same interface
> of course) and it should be faster in this way.
> The I will do some serious testing on ratw vs. no of classes.

> 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?

> Also limiting is packet rate not byte rate .. The limit is somewhere
> at 30000 packets per second for both CBQ and HTB with 5 classes which
> is cca 500Mbit for 1.5k packets (on my PII).
	But ultimately its going to limit on byte transfer, isn't it?

-- Sumit

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

  parent reply	other threads:[~2002-02-15  9:22 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 [this message]
2002-02-15 12:01 ` Martin Devera
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-101377301614886@msgid-missing \
    --to=sumit@elitecore.com \
    --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.