All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Emmanuel SIMON" <manu@host.fr>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] Some questions remaining about TC
Date: Wed, 11 Jun 2003 10:26:21 +0000	[thread overview]
Message-ID: <marc-lartc-105532726830295@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105519389407466@msgid-missing>

First, thank you Stef for answering.
That's what I understood. I think my question was not enough precise (??)

My reel question/problem is why are parameters of the bandwidth (such as
rate, burts ...) set on classes rather than on qdiscs ?
I guess a class should only map a flow and should not know how this flow
will be sent. Especially that classes don't send packets. What is the reason
why it is done so ? And what if i don't specify parameters fir a leaf class
? Does it herit from the parent ?

Thanks once more
Manu

> -----Message d'origine-----
> De : lartc-admin@mailman.ds9a.nl
> [mailto:lartc-admin@mailman.ds9a.nl]De
> la part de Stef Coene
> Envoyé : mardi 10 juin 2003 20:55
> À : Emmanuel SIMON; lartc@mailman.ds9a.nl
> Objet : Re: [LARTC] Some questions remaining about TC
>
>
> On Monday 09 June 2003 23:18, Emmanuel SIMON wrote:
> > Hello everybody,
> >
> > I try to work with TC for a little while in my study and
> there still are a
> > few questions that I can\'t find any answer anywhere.
> >
> > Firts about qdisc and classes:
> >  - What is exactly the difference between qdsic and class ? They are
> > so \"intimately tied together\" that i\'m not sure not make
> the difference.
> > Why can\'t we have a qdsic HTB with a class CBQ within or reverse.
> >  - We have classes but is there any heritage (i\'m not sure
> it is the right
> > word) somewhere: between qdiscs, between classes or between
> qdiscs and
> > classes.
> A qdisc is a structure where a packet can be enqueued.  The
> most important is
> the root qdisc.  That's the qdisc that will proces all
> packets leaving a NIC.
> If you have classfull qdisc you can add classes.  A class
> will hold some part
> of the traffic.  So all packets leaving a nic are enqueued in
> the root qdisc
> and will be "forwarded" to a class.  Each class has 1 qdisc
> attached to it.
> So it's the qdisc attached to a class that will reponsible
> for sending the
> packet
>
> Sorry, can't help you with your other questions.
>
> 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/
>

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

  parent reply	other threads:[~2003-06-11 10:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-09 21:18 [LARTC] Some questions remaining about TC Emmanuel SIMON
2003-06-10 18:55 ` Stef Coene
2003-06-11  7:41 ` Lars Landmark
2003-06-11 10:26 ` Emmanuel SIMON [this message]
2003-06-11 16:47 ` Stef Coene

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-105532726830295@msgid-missing \
    --to=manu@host.fr \
    --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.