Linux Advanced Routing and Traffic Control list
 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:36:48 +0000	[thread overview]
Message-ID: <marc-lartc-98578662319467@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98567886104582@msgid-missing>

Hi,

> > 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?
> 
> There are other minor details (hence my suggestion to read the paper
> because i cant remember details),

Maybe I will read it some day ;-)

> but fixing the deficit such that you
> take into consideration 'byte credit' a queue has when you preempt it
> makes a WRR implementation closer to DRR.

Well, the WRR qdisc essentially works this way:

* For each band (=class) there is a byte counter
* When a band transfers a packet the byte counter is increased by the packet size divided with the weight (which is a number between 0 and 1)
* The next band that can transfer a packet is always the one with the lowest byte counter.

It also does some additional things to make sure that when a new band has something to send it can send it immedialty. I don't see any way this scheme can be improved.

> > 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.
> 
> The original CBQ implementation is the classical WRR;

But it did not take the packet size into account?

> Note there have been attempts to document Linux CBQ; search the mailing
> list.

Hmm, interesseting, maybe I should subscribe to the linux-diffserv mailing list. 


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:36 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
2001-03-28 13:24 ` jamal
2001-03-28 13:36 ` Christian Worm Mortensen [this message]
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-98578662319467@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox