All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leandro Stasi <kinyo@sinectis.com.ar>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] cbq (root class) rate problem]
Date: Tue, 07 May 2002 17:07:48 +0000	[thread overview]
Message-ID: <marc-lartc-102079137107289@msgid-missing> (raw)




Stef Coene wrote:

 >>I did a workaround by creating an extra class with root class as parent
 >>and isolated,bounded
 >>
 >>
 >>But I don't like to have extra classes just becuse I can control root
 >>class.
 >>
 >>tc qdisc  add dev eth0 root handle 10:0 cbq bandwidth 10mbit avpkt 1000
 >>cell 8
 >>
 >>tc class  add dev eth0 parent 10:0 classid 10:1 cbq bandwidth 10mbit
 >>rate 50kbit allot 1514 cell 8 maxburst 20 avpkt 1000 isolated bounded
 >>
 >>tc class  add dev eth0 parent 10:1 classid 10:10 cbq bandwidth 10mbit
 >>rate 25kbit allot 1514 cell 8 maxburst 20 avpkt 1000 sharing borrow
 >>
 >>tc class  add dev eth0 parent 10:1 classid 10:11 cbq bandwidth 10mbit
 >>rate 25kbitallot 1514 cell 8 maxburst 20 avpkt 1000 sharing borrow
 >>
 > This is the way you should do it.  That extra class is no problem. 
You can
 > remove the sharing and borrow parameter if you want.  They are on by 
default.
 >
 > Also provide a weight parameter (I take weight = rate/2) and attach the
 > filters to the root qdisc and point them direclty to the end class.
 >
 > Stef
 >
 >



It is useless to attach a qdisc (like sfq) to the extra class?

What is the difference between attaching the filter to the root qdisc or
to the leaf classes?




_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2002-05-07 17:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-07 17:07 Leandro Stasi [this message]
2002-05-07 18:07 ` [LARTC] cbq (root class) rate problem] 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-102079137107289@msgid-missing \
    --to=kinyo@sinectis.com.ar \
    --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.