All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Classes and qdiscs
Date: Thu, 13 Mar 2003 16:04:16 +0000	[thread overview]
Message-ID: <marc-lartc-104757156126740@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104751711907943@msgid-missing>

On Thursday 13 March 2003 01:57, S Mohan wrote:
> I've been reading the posts on classless queuing and classes/qdisc
> combinations. Both Martin and Stef mentioned that one class can have
> more than one qdisc attached.
No.  One class can has 1 qdiac attached.  But there are qdiscs with multiple 
classes and you can add a qdisc to each of these classes.

> The way I had understood queue disciplines was as follows:
>
> 1. A class has a qdisc to regulate traffic under limit e.g htb/tbf....
Not really.  The qdisc is only responsible for sending the traffic that 
belongs to that class.

> 2. A tier in the hierarchy has a qdisc attached for sharing of spare
> bandwidth not utilized by one or more classes amongst the others in the
> same tier.
>
> Or would it be correct to say that each class has a qdisc that
> distributes its spare bandwidth to others in the same level in the
> hierarchy? Does it mean that if I have SFQ for one class and have not
> attached SFQ to the other two classes at the same level, the other two
> classes would get even distribution of bandwidth not utilized by the
> first class?
Classes are responsible for managing the traffic.  Each class sholds a part of 
the total traffic.  Unused bandwidth can be shared amongs the differenc 
classes.
If you want to understand how traffic is managed between classes, forget about 
the qdiscs.  Just think about the classes.  The qdiscs are only responsible 
for sending the traffic.  The amount of traffic is regulated by the 
configuration of the classes.

Stef


-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

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

  reply	other threads:[~2003-03-13 16:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-13  0:58 [LARTC] Classes and qdiscs S Mohan
2003-03-13 16:04 ` Stef Coene [this message]
2005-03-29 19:40 ` [LARTC] classes " Marcus Fritzsch
2005-04-04 12:59 ` Andy Furniss
2005-04-05 22:24 ` Andy Furniss

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-104757156126740@msgid-missing \
    --to=stef.coene@docum.org \
    --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.