From: Andreas Klauer <Andreas.Klauer@metamorpher.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] classless qdisc and classful qdisc
Date: Sun, 22 Jan 2006 17:08:03 +0000 [thread overview]
Message-ID: <20060122170803.GA12539@EIS> (raw)
In-Reply-To: <75dbe4850601220407h44b99847p28258c5409dc6353@mail.gmail.com>
On Sun, Jan 22, 2006 at 07:07:32PM +0700, Ismail Fahmi wrote:
> 1. what is the difference between classless and classful qdisc?? when I made
> a qdisc, are I must create both of that qdisc...???
A classful qdisc allows packets to be sorted into different groups, and to
handle packets differently depending on the group they belong to. This gives
you a lot of control over how packets of a certain type / belonging to a
certain user / etc. should be treated.
A classless qdisc just takes all incoming packets and treats them essentially
all the same (with some exceptions). You can't manually customize or group
type of packets in any way.
> 2. what is the difference beetween three of the classless qdisc in linux
> redhat 2.4, sfq pfifo and tbf if I using the htb classful qdisc ??? because
> when I use htb classful qdisc it means I made a qdisc that can rate b/w for
> each class, so it's no difference between I used tbf classless qdisc in each
> class and I used sfq or pfifo...
Not sure if I got this question right. Are you asking what the difference
between limiting bandwidth using HTB and TBF is? In that case, TBF is classless,
doesn't know anything at all about other traffic, and will just stupidly limit
the bandwidth to a certain value. HTB on the other hand knows about its classes
and can balance the total available bandwidth between them.
HTH
Andreas Klauer
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2006-01-22 17:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-22 12:07 [LARTC] classless qdisc and classful qdisc Ismail Fahmi
2006-01-22 17:08 ` Andreas Klauer [this message]
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=20060122170803.GA12539@EIS \
--to=andreas.klauer@metamorpher.de \
--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.