From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] exploring HTB
Date: Wed, 13 Feb 2002 15:05:10 +0000 [thread overview]
Message-ID: <marc-lartc-101361275306624@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101361106601378@msgid-missing>
> 2> Manual states that "... ... ... Now we can optionally attach queuing
> disciplines to the leaf classes... ... ... tc qdisc add dev eth0 parent
> 1:10 handle 20: pfifo limit 5... ... ...". If I not going to do that still
> I'm fine with my rule set, as written "optional". Then is there benefit or
> payoff against this leaf-class?
Each class has a qdisc attached. By default, this is a FIFO one (First In,
First Out). You can replace it with a SFQ qdisc. A SFQ qdisc will treath
each flow with the same priority. So one flow can not eat all bandwidth.
> 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?
Can't find that page.
>
> 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 think you can shape a lot of traffic with this setup, but I don't know
exactly.
Stef
--
stef.coene@docum.org
More QOS info : http://www.docum.org/
Title : "Using Linux as bandwidth manager"
_______________________________________________
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-13 15:05 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 [this message]
2002-02-14 10:59 ` Martin Devera
2002-02-15 9:22 ` Sumit Pandya
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-101361275306624@msgid-missing \
--to=stef.coene@docum.org \
--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.