Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Anton Yurchenko <phila@dg.net.ua>
To: lartc@vger.kernel.org
Subject: [Fwd: Re: [LARTC] borrowing only from parent]
Date: Fri, 26 Apr 2002 10:56:31 +0000	[thread overview]
Message-ID: <marc-lartc-101981864904728@msgid-missing> (raw)

[-- Attachment #1: Type: text/plain, Size: 1 bytes --]



[-- Attachment #2: Re: [LARTC] borrowing only from parent --]
[-- Type: message/rfc822, Size: 2446 bytes --]

From: Martin Devera <devik@cdi.cz>
To: Anton Yurchenko <phila@dg.net.ua>
Cc: lartc@mailman.ds9a.nl
Subject: Re: [LARTC] borrowing only from parent
Date: Fri, 26 Apr 2002 12:48:08 +0200 (CEST)
Message-ID: <Pine.LNX.4.44.0204261247180.12674-100000@luxik.cdi.cz>

If you read the manual, the algorithm will not work correctly
with {,c}burst < MTU ...
devik

On Fri, 26 Apr 2002, Anton Yurchenko wrote:

>
> Hello,
>
> for example I have a parent class 1:1 defined as:
>
> tc qdisc add dev eth0 root handle 1: htb default 12
>
> # shape at 15 kbit almost no borrowing and no bursts
> tc class add dev eth0 parent 1: classid 1:1 htb rate 15kbit ceil 1kbit burst 1b cburst 1b

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


             reply	other threads:[~2002-04-26 10:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-26 10:56 Anton Yurchenko [this message]
2002-04-26 10:57 ` [Fwd: Re: [LARTC] borrowing only from parent] Anton Yurchenko
2002-04-26 10:57 ` Anton Yurchenko
2002-04-26 11:17 ` Martin Devera
2002-04-26 11:26 ` Anton Yurchenko
2002-04-26 11:31 ` Martin Devera
2002-04-26 11:54 ` Anton Yurchenko
2002-04-26 12:09 ` Martin Devera
2002-04-26 12:24 ` Anton Yurchenko
2002-04-26 12:28 ` Martin Devera
2002-05-15  6:57 ` Herman Cremer
2002-05-15  7:07 ` Herman Cremer

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-101981864904728@msgid-missing \
    --to=phila@dg.net.ua \
    --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