Linux Advanced Routing and Traffic Control list
 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: Thu, 30 Oct 2003 05:54:51 +0000	[thread overview]
Message-ID: <marc-lartc-106749375911500@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106732522922215@msgid-missing>

Hi,
--- Stef Coene <stef.coene@docum.org> wrote:
> A qdisc is a queueing discipline : it's a queue for
> packets.  A class is 
> something virtual that hold some packets from that
> queue.
okey, I must say I have a better understanding of the
differences now. Thank you. 

> > okey, so ideally for a bandwidth that varies (by
> few
> > bytes) cbq is the best available?
> No, you will have the same problem with cbq :(
so which kind of qdisc will be best for varing
bandwidths?

Thank you, Stef.

Regards,
suraj.

__________________________________
Do you Yahoo!?
Exclusive Video Premiere - Britney Spears
http://launch.yahoo.com/promos/britneyspears/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2003-10-30  5:54 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
2003-10-29 18:41 ` Stef Coene
2003-10-29 18:59 ` Stef Coene
2003-10-30  5:54 ` Suraj Shankar [this message]
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-106749375911500@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox