From: "Steen Suder, privat" <sfs_lartc@suder.dk>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] "Fan-in/fan-out" tc filters?
Date: Wed, 13 Nov 2002 20:37:31 +0000 [thread overview]
Message-ID: <marc-lartc-103721992601604@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103721093821681@msgid-missing>
Stef Coene wrote:
>>I'd like to do that to make sure that the system overall favours
>>interactive traffic before "bulk". Games and other latency-dependant
>>traffic types must perform the best on the cost of ftp-download or similar.
>>
>>Attaching pfifo_fast, PRIO or triple (low/medium/high priorities) HTB
>>qdiscs to the root is easy but it seems that it is impossible to attach
>>/one/ WRR afterwards.
>
> What do you mean with WRR? Weighted Round Robin? Or the wrr qdisc?
The qdisc wrr. It has the possibility to set "penalty" through different
weigths.
> If you want to improve latency for certain traffic, you can create 2 htb
> classes. One with a lower prio parameter to get low latency and an other
> class with all other traffic.
> To give each pc on the network the same opportunity to send something, create
> 100 sub classes with parent=second class. To get fairness / pc, you can add
> a sfq to each class. You can do the same for the low prio class. If you
> don't care about fairness / pc, you can add 1 esfq qdisc instead of the 100
> sub classes.
I want to make sure that given an assortment of packets containing
different kinds of traffic, say game and download, the game packets will
be in front of the download packets when they are dequeued from the
leafs of the wrr qdisc.
The idea was to have all traffic go through the same wrr qdisc. They
just had to "reordered" before going to the wrr qdisc. Does that make sense?
Partly derived suggestion:
DEV
|
---------
| HTB | "Bottleneck" - needed
---------
|
|
-------|
/ |
/ |
/ |
-------- --------
| HS | | BULK | HS = High Speed, low latency
-------- -------- Bulk = The rest
| |
-------- |
| SFQ | | Maybe a complementary SFQ?
-------- |
|
|
-------
| WRR | wrr qdisc - needed to give
------- instant penalties to heavy
| downloaders
|
-------|--------
/ | \
/ | \
/ | \
------- ------- -------
| SFQ | | SFQ | | SFQ | x 100
------- ------- -------
This solution could very well give better performance for the filtered,
interactive traffic. I just have to make sure that the volume i HS
doesn't get to big to keep users happy.
They're so picky ;-)
--
Mvh. / Best regards,
Steen Suder <http://www.suder.dk/>
ICQ UIN 4133803
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-11-13 20:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-13 18:07 [LARTC] "Fan-in/fan-out" tc filters? Steen Suder, privat
2002-11-13 18:25 ` Stef Coene
2002-11-13 19:58 ` Christian G. Warden
2002-11-13 20:37 ` Steen Suder, privat [this message]
2002-11-13 21:24 ` Stef Coene
2002-11-13 21:32 ` 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-103721992601604@msgid-missing \
--to=sfs_lartc@suder.dk \
--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.