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@xxxxxxxxxxxxxxx > [mailto:lartc-admin@xxxxxxxxxxxxxxx]De > la part de Stef Coene > Envoyé : mardi 10 juin 2003 20:55 > À : Emmanuel SIMON; lartc@xxxxxxxxxxxxxxx > 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@xxxxxxxxx > "Using Linux as bandwidth manager" > http://www.docum.org/ > #lartc @ irc.oftc.net > > _______________________________________________ > LARTC mailing list / LARTC@xxxxxxxxxxxxxxx > http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/ >
