From: "GoMi" <gomiuk@hotmail.com>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] TC with HTB qdisc
Date: Sun, 20 Apr 2003 21:48:58 +0000 [thread overview]
Message-ID: <marc-lartc-105087565226457@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105083667104605@msgid-missing>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
That might work for 2 or 5 or even 10 hosts, but what about 150 hosts? I do have 150 users, should i create 150 classes? I have an AMD DURON 800. Would that work? I can create an script to do so, but i am worried about CPU load
- -----Mensaje original-----
De: lartc-admin@mailman.ds9a.nl [mailto:lartc-admin@mailman.ds9a.nl] En nombre de Stef Coene
Enviado el: domingo, 20 de abril de 2003 23:41
Para: Rio Martin.; lartc@mailman.ds9a.nl
Asunto: Re: [LARTC] TC with HTB qdisc
On Sunday 20 April 2003 13:03, Rio Martin. wrote:
> Dear folks,
> Is there anyone succeed implementing traffic management using htb
> qdisc, specially implementing fair sharing among 2 hosts at the same
> speed ? I wonder why me, and lots of my friend from different ISP
> having the same problem just like me ? If their clients start to open
> pararel connection like Kazaa or DAP (Download Accelerator Pro), they
> borrowed bandwidth from their parent and when the other request more
> bandwidth from parent, parent didnt decrease the speed of first host
> who started DAP ?
If you put each host in a different class, all traffic from the hosts are
considered ase one. So if 1 hosts generates 100 tcp streams and the other
hosts 1, the 100 streams are considered as 1.
I did the test, I create 2 classes with each 50% of the bandwidth. I
generated 5 streams in the first class. As soon as I generate a tcp stream
in the other class, the other class gets 50% of the bandwidth
So if you put each host in his own class, you should be fine.
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/
-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0
iQA/AwUBPqMVyX7diNnrrZKsEQLsTACfaL1dhoGs2FR+62h1m56yZnmHstYAoOkJ
2qgY7nUPIhmhx6uT13846QvV
=KW0v
-----END PGP SIGNATURE-----
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-04-20 21:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-20 11:03 [LARTC] TC with HTB qdisc Rio Martin.
2003-04-20 21:40 ` Stef Coene
2003-04-20 21:48 ` GoMi [this message]
2003-04-20 21:58 ` Stef Coene
2003-04-20 23:52 ` GoMi
2003-04-21 9:10 ` 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-105087565226457@msgid-missing \
--to=gomiuk@hotmail.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.