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: Wed, 28 Mar 2001 12:43:07 +0000	[thread overview]
Message-ID: <marc-lartc-98578350611172@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98567886104582@msgid-missing>



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

>
> Yes, but in the howto also a qdisc named WRR is mentioned.

What HOWTO? Is this one of those schedulers that Martin wrote? Never
paid much attention; Maybe because i never thought that WRR was important
once we had DRR.

>
> A quick search on Google BTW said that DRR is only better in terms
> of speed of the implementation but is worse in terms distribution bandwidth.

WRR works well when you apriori know the packet/cell sizes (eg in ATM).
If you cant do this, then WRR is unfair once you start having a lot of
flows going or you mistweak your weights etc. DRR fixes this. The
improvements on computation comes in as a bonus _not_ as the advantage of
DRR over WRR.
Why dont you read the classical paper at:
http://www.acm.org/sigcomm/sigcomm95/papers/shreedhar.html

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-28 12:43 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
2001-03-27 15:23 ` Christian Worm Mortensen
2001-03-28 12:43 ` jamal [this message]
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-98578350611172@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