All of lore.kernel.org
 help / color / mirror / Atom feed
* [LARTC] Internal Qdisc
@ 2005-04-27 10:23 R Harper
  2005-04-27 10:41 ` Leo
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: R Harper @ 2005-04-27 10:23 UTC (permalink / raw)
  To: lartc

Hell
I'm new to Qdisc programming and I was wondering, what is the difference 
between using an internal Qdisc (like e.g. TBF does) vs. not using internal 
Qdisc (like e.g. SFQ does)?

Can someone give me a quick rundown of pro and cons?

with regards
R.harper

_________________________________________________________________
Undgå pop-ups med MSN Toolbar -  http://toolbar.msn.dk hent den gratis!

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [LARTC] Internal Qdisc
  2005-04-27 10:23 [LARTC] Internal Qdisc R Harper
@ 2005-04-27 10:41 ` Leo
  2005-04-27 11:00 ` R Harper
  2005-04-27 11:34 ` Patrick McHardy
  2 siblings, 0 replies; 4+ messages in thread
From: Leo @ 2005-04-27 10:41 UTC (permalink / raw)
  To: lartc

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="windows-1252", Size: 978 bytes --]

Hi

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.

Leo

R Harper wrote:
> Hell
> I'm new to Qdisc programming and I was wondering, what is the difference
> between using an internal Qdisc (like e.g. TBF does) vs. not using
> internal Qdisc (like e.g. SFQ does)?
> 
> Can someone give me a quick rundown of pro and cons?
> 
> with regards
> R.harper
> 
> _________________________________________________________________
> Undg\x7f pop-ups med MSN Toolbar -  http://toolbar.msn.dk hent den gratis!
> 
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
> 
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [LARTC] Internal Qdisc
  2005-04-27 10:23 [LARTC] Internal Qdisc R Harper
  2005-04-27 10:41 ` Leo
@ 2005-04-27 11:00 ` R Harper
  2005-04-27 11:34 ` Patrick McHardy
  2 siblings, 0 replies; 4+ messages in thread
From: R Harper @ 2005-04-27 11:00 UTC (permalink / raw)
  To: lartc

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="windows-1252", Size: 1562 bytes --]

>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....

But thanks for your reply

Regards
R.Harper


>R Harper wrote:
> > Hell
> > I'm new to Qdisc programming and I was wondering, what is the difference
> > between using an internal Qdisc (like e.g. TBF does) vs. not using
> > internal Qdisc (like e.g. SFQ does)?
> >
> > Can someone give me a quick rundown of pro and cons?
> >
> > with regards
> > R.harper
> >
> > _________________________________________________________________
> > Undg\x7f pop-ups med MSN Toolbar -  http://toolbar.msn.dk hent den gratis!
> >
> > _______________________________________________
> > LARTC mailing list
> > LARTC@mailman.ds9a.nl
> > http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
> >

_________________________________________________________________
Få alle de nye og sjove ikoner med MSN Messenger http://messenger.msn.dk/

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [LARTC] Internal Qdisc
  2005-04-27 10:23 [LARTC] Internal Qdisc R Harper
  2005-04-27 10:41 ` Leo
  2005-04-27 11:00 ` R Harper
@ 2005-04-27 11:34 ` Patrick McHardy
  2 siblings, 0 replies; 4+ messages in thread
From: Patrick McHardy @ 2005-04-27 11:34 UTC (permalink / raw)
  To: lartc

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2005-04-27 11:34 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-04-27 10:23 [LARTC] Internal Qdisc R Harper
2005-04-27 10:41 ` Leo
2005-04-27 11:00 ` R Harper
2005-04-27 11:34 ` Patrick McHardy

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.