All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Over value in CEIL parameter..
Date: Thu, 24 Jul 2003 16:28:00 +0000	[thread overview]
Message-ID: <marc-lartc-105940882906052@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105893713024294@msgid-missing>

On Thursday 24 July 2003 04:22, Rio Martin. wrote:
> On Wednesday 23 July 2003 21:16, Stef Coene wrote:
> > On Wednesday 23 July 2003 07:40, Martin A. Brown wrote:
> > > [ Stef may have more to say about this. ]
> >
> > 132kbit - 128kbit = 4kbit and that's not much.  So I don't think you have
> > to worry.
> > Is this ceil parameter on a leaf class (a class with no child classes)? 
> > Or can you post you script?
> > Also, execute tc -s -d clas sshow dev eth0 and watch the ctokens.  They
> > should never be negative for that class.
>
> Yes, the ceil parameter on leaf class.
> I tried Martin's way by setting Burst and Cburst value to zero.
> And the value of bps exceed CEIL parameter around 50 - 80 bps.
Can you post your script and the output of tc -s -d class show dev eth0?

Stef

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

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

  parent reply	other threads:[~2003-07-24 16:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-23  5:14 [LARTC] Over value in CEIL parameter Rio Martin.
2003-07-23  5:40 ` Martin A. Brown
2003-07-23  6:53 ` Rio Martin.
2003-07-23 14:16 ` Stef Coene
2003-07-24  2:22 ` Rio Martin.
2003-07-24 16:28 ` Stef Coene [this message]
2003-07-29  5:28 ` Rio Martin.
2003-07-29  7:45 ` 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-105940882906052@msgid-missing \
    --to=stef.coene@docum.org \
    --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.