All of lore.kernel.org
 help / color / mirror / Atom feed
From: Walter Haidinger <walter.haidinger@gmx.at>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] htb limiting trouble: no overlimit or dropped packets
Date: Thu, 17 Oct 2002 06:38:54 +0000	[thread overview]
Message-ID: <marc-lartc-103483684722313@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103480767301168@msgid-missing>

On Thu, 17 Oct 2002, Stephane Ouellette wrote:

>    I'm giving a try on this one, I'm not familiar with HTB at all...

Thanks, I appreciate that!

>    I think that your only problem is: all classes can borrow bandwidth
> from other classes !!  So there is no bandwidth control !

Yes, but there is a ceiling of 64 kbit/s set for each class. Yet this is
exceeded and traffic flows with full 512 kbit/s.

Besides, if you have a look at the class statistics you'll find that the
borrowed packet counts remain at a value of zero.

>    You should add the "bounded" modifier to classes that should be limited.

AFAIK there is no bounded (or isolated, borrow, etc like in CBQ)
option with htb. From the htb manpage:

       tc class  ...  dev  dev  parent  major:[minor]  [  classid
       major:minor  ]  htb  rate rate [ ceil rate ] burst bytes [
       cburst bytes ] [ prio priority ]

Regards, Walter

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

  parent reply	other threads:[~2002-10-17  6:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-16 22:33 [LARTC] htb limiting trouble: no overlimit or dropped packets Walter Haidinger
2002-10-17  4:49 ` Stephane Ouellette
2002-10-17  6:38 ` Walter Haidinger [this message]
2002-10-17  6:47 ` Walter Haidinger
2002-10-17 10:54 ` Stef Coene
2002-10-17 11:19 ` Walter Haidinger
2002-10-17 18:02 ` Robert Vale
2002-10-17 19:24 ` Walter Haidinger
2002-10-17 20:44 ` Walter Haidinger
2002-10-20 12:18 ` Walter Haidinger
2002-10-20 17:18 ` Walter Haidinger

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-103483684722313@msgid-missing \
    --to=walter.haidinger@gmx.at \
    --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.