Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: jamal <hadi@cyberus.ca>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] CBQ and WRR
Date: Tue, 27 Mar 2001 12:05:05 +0000	[thread overview]
Message-ID: <marc-lartc-98569482211429@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98567886104582@msgid-missing>



On Tue, 27 Mar 2001, Christian Worm Mortensen wrote:

> The WRR qdisc mentioned in the howto has never been a part of the standard kernel.

Linux CBQ actually _does_ implement a WRR variant known as DRR (Deficit
Round Robin). DRR is better than classical WRR. Read the Varghese paper
to see the difference.

In any case to the original poster: You can look at qdiscs as building
blocks with a well known interface and that are defined to provide a
certain specific 'service' to packets travessing them.
They could be schedulers like Prio or markers like dsmark or active queue
management schemes like GRED. Normally there is an associate queue with
a queing discipline although sometimes not directly owned by the qdisc
rather by other embedded qdiscs (eg prio with attached FIFO qdiscs).

cheers,
jamal


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

  parent reply	other threads:[~2001-03-27 12:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-27  7:49 [LARTC] CBQ and WRR Rick Goh
2001-03-27  8:26 ` Christian Worm Mortensen
2001-03-27 12:05 ` jamal [this message]
2001-03-27 15:23 ` Christian Worm Mortensen
2001-03-28 12:43 ` jamal
2001-03-28 13:03 ` Christian Worm Mortensen
2001-03-28 13:24 ` jamal
2001-03-28 13:36 ` Christian Worm Mortensen
2001-03-28 13:59 ` jamal
2001-03-28 14:22 ` Christian Worm Mortensen

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-98569482211429@msgid-missing \
    --to=hadi@cyberus.ca \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox