All of lore.kernel.org
 help / color / mirror / Atom feed
From: Suraj Shankar <su_raj_in@yahoo.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Explanation reqd. for few (more than few!) concepts in TC <long>
Date: Wed, 29 Oct 2003 15:07:19 +0000	[thread overview]
Message-ID: <marc-lartc-106744053718076@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106732522922215@msgid-missing>

Hi,
--- "Michael T. Babcock" <mbabcock@fibrespeed.net>
wrote:
 
> If I may Stef, a qdisc is short for a Queuing
> Discipline.  It determines 
> how a packet leaves itself.  A FIFO qdisc is
> basically what you have if 
> you don't use one at all; every packet comes in,
> lines up, and spits out 
> in the same order.
> 
> You can add classifiable queuing disciplines
> however.  Such a queuing 
> discipline allows you to add classes to it.  Each
> class is like a branch 
> in a tree.  When you get to the end of the branch
> you have a leaf and 
> that needs a queuing discipline again.
> 
> Whether it would work or not is one thing, but
> technically speaking, you 
> could add an HTB (classful) qdisc to eth0, then make
> a tree of classes 
> under that.  Then some of those could have SFQ or
> RED qdisc's attached 
> to them (the end leaves of the tree) and others
> could have another tree 
> added as HTB or CBQ even (also classful).
yes! somebody does think like I do ... but isn't there
a valid reason why a class is called a class and a
qdisc called a qdisc?!?

Thank you.

Regards,
suraj.

__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2003-10-29 15:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-28  7:06 [LARTC] Explanation reqd. for few (more than few!) concepts in TC <long> Suraj Shankar
2003-10-28 18:08 ` Stef Coene
2003-10-28 18:08 ` Damjan
2003-10-29 14:23 ` Suraj Shankar
2003-10-29 15:02 ` Suraj Shankar
2003-10-29 15:07 ` Suraj Shankar [this message]
2003-10-29 18:41 ` Stef Coene
2003-10-29 18:59 ` Stef Coene
2003-10-30  5:54 ` Suraj Shankar
2003-10-30  6:10 ` Suraj Shankar
2003-10-30 10:38 ` Stef Coene
2003-10-30 10:43 ` Stef Coene
2003-10-31  7:23 ` Suraj Shankar
2003-10-31  9: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-106744053718076@msgid-missing \
    --to=su_raj_in@yahoo.com \
    --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.