From: Junus Junarto junus@mail.com
To: lartc@vger.kernel.org
Subject: [LARTC] traffic shaping
Date: Fri, 05 Jan 2001 13:56:04 +0000 [thread overview]
Message-ID: <marc-lartc-98373940416825@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373940416818@msgid-missing>
<PRE>To make dynamic balance traffic shaping, maybe we can use WRR quequing.
You can look at: Linux 2.4 Advanced Routing Howto; section 9.6
Or you can go directly to <A HREF="http://wipl-wrr.dkik.dk/wrr">http://wipl-wrr.dkik.dk/wrr</A>
Regards,
Junus Junarto D
Date: Fri, 05 Jan 2001 04:52:54 +0100
><i> To: "Wouter Smit" <<A HREF="mailto:wouter@smit.dhs.org">wouter@smit.dhs.org</A>>
</I>><i> From: Sander <<A HREF="mailto:thrill12@gmx.net">thrill12@gmx.net</A>>
</I>><i> Subject: Re: [LARTC] traffic shaping
</I>><i> So we now have 1 root class of 128 kbit, two subclasses of 64 kbit, each
</I>of
><i> those subclass serving 3 people.
</I>><i> The 40kbit per person thing was done with one purpose: when 1 person
</I>starts
><i> the upload, and another person kicks in, the first person still gets
</I>><i> 128Kbit - 40Kbit and the second one gets that 40 Kbit. This is more then
</I>><i> one would get when we would simply divide 128Kbit by 6. I don't yet know
</I>><i> how to get the loadbalancing system to divide the space evenly (1
</I>><i> person\x128 Kbit, 2 persons = 64Kbit, 3CKbit etc..), but haven't come up
</I>><i> with a solution yet.
</I>
______________________________________________
FREE Personalized Email at Mail.com
Sign up at <A HREF="http://www.mail.com/?sr=signup">http://www.mail.com/?sr=signup</A>
</PRE>
next prev parent reply other threads:[~2001-01-05 13:56 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-04 12:22 [LARTC] traffic shaping Wouter
2001-01-04 18:17 ` Sander
2001-01-05 3:52 ` Sander
2001-01-05 11:42 ` Wouter
2001-01-05 13:56 ` Junus [this message]
2001-01-05 13:56 ` Junus
2001-01-06 9:25 ` [LARTC] Traffic shaping Bruno
2001-01-07 13:54 ` Junus
2001-12-25 12:15 ` [LARTC] Traffic Shaping Sahil Gupta - NET4U
2001-12-25 12:27 ` bert hubert
2001-12-25 12:33 ` Sahil Gupta - NET4U
2001-12-25 12:34 ` Sahil Gupta - NET4U
2001-12-25 12:42 ` bert hubert
2002-01-22 4:52 ` [LARTC] traffic shaping Antonis Lazaridis
2002-01-22 7:44 ` Martin Devera
2002-01-23 8:23 ` Martin Devera
2002-01-23 9:42 ` Antonis Lazaridis
2002-01-23 9:51 ` Martin Devera
2002-01-25 8:11 ` Antonis Lazaridis
2002-01-26 23:00 ` Martin Devera
2002-01-27 1:21 ` Re[2]: " Will Lotto
2002-01-27 8:47 ` Stef Coene
2002-02-08 5:17 ` Antonis Lazaridis
2002-02-08 17:22 ` Riaz Mahmood
2006-10-04 20:45 ` Roberto Scattini
2007-05-06 20:14 ` [LARTC] Traffic Shaping Rangi Biddle
2007-05-07 8:25 ` AW: " Simo
2007-05-07 18:06 ` Rangi Biddle
2007-05-08 3:16 ` Rangi Biddle
2007-10-24 18:37 ` [LARTC] Traffic shaping Mohammad Shakir
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-98373940416825@msgid-missing \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox