From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stef Coene Date: Tue, 10 Jun 2003 18:55:12 +0000 Subject: Re: [LARTC] Some questions remaining about TC Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: lartc@vger.kernel.org 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/