All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian Worm Mortensen" <worm@dkik.dk>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] CBQ and WRR
Date: Wed, 28 Mar 2001 13:03:54 +0000	[thread overview]
Message-ID: <marc-lartc-98578464814021@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98567886104582@msgid-missing>

Hi,

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

This thread is on two mailing lists. One of the lists is for the howto located on http://ds9a.nl/2.4Routing/. This howto mentions the WRR qdisc (see http://wipl-wrr.dkik.dk/wrr/) which is a qdisc that is _not_ included in the standard kernel and has nothing to do with CBQ.

> 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.

Hmm... Maybe you talk about how WRR/DRR is implemented in CBQ? A pure WRR scheduler works perfect no matter what size the packets have. If, of course, the scheduler takes packet sizes into account. What exactly is the problem with a WRR scheduler? 

Another thing: Unless you have a need to give special traffic very low delay I don't see any reason why you would want to use CBQ instead of pure WRR? I.e.: If you use CBQ with all prio parameters set to the same, why not use pure WRR instead?

> Why dont you read the classical paper at:
> http://www.acm.org/sigcomm/sigcomm95/papers/shreedhar.html

What I really need is a paper describing CBQ in Linux - the original article desribing CBQ is very generel. And when I experimented with CBQ the last time I did not see the behaviour I would exepect from the article assuming that the generel scehudler was a WRR scheduler.


Christian


_______________________________________________
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 13:03 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
2001-03-28 13:03 ` Christian Worm Mortensen [this message]
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-98578464814021@msgid-missing \
    --to=worm@dkik.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.