From mboxrd@z Thu Jan 1 00:00:00 1970 From: Patrick McHardy Date: Wed, 27 Apr 2005 11:34:38 +0000 Subject: Re: [LARTC] Internal Qdisc Message-Id: <426F78CE.7080603@trash.net> 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 R Harper wrote: >> TBF provides traffic shaping by the Token Bucket theory, while SFQ makes >> sure(actually just hints) swap packets in different sessions so that no >> particular session will hang around for a long time. > > > Yes I know the difference between TBF and SFQ. > > I was trying to ask about the programming/architectural difference > between creating a *internal Qdisc* for buffering (like TBF does) and > then using > q->qdisc->enqueue(skb, q->qdisc) etc. commands for queueing ... > > or just use the qdisc "provided"? > __skb_enqueue(skb, skq->q) etc commands for queueing.... Internal qdiscs don't show up in dev->qdisc_list and thus are invisible to ip qdisc show. They're usually used as place-holder leaf qdiscs until the user configures a different one. SFQ doesn't use them to fit all internal queues in one page. Regards Patrick _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc