All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Leyva <aleyva@pichon.df.gob.mx>
To: lartc@vger.kernel.org
Subject: [LARTC] Determining tbf parameters
Date: Fri, 22 Mar 2002 18:49:26 +0000	[thread overview]
Message-ID: <marc-lartc-101682297718443@msgid-missing> (raw)

Hi, im doing something like this:
tc qdisc add $DEV parent 1:110 handle 110: estimator 1sec 8sec \
        tbf rate 1Mbit burst ??? limit ???

I've been triying with diferent values for burst, limit and latency, but
we cant understand how to determine the correct values for them.

In "Short evaluation of linux token-bucket-filter queueing discipline"
by Kurt Wagner we learned that queue size=limit+bucket size, but we dont
know how to determine limit, burst and latency.

We found different formulas to determine the size of the bucket, the
latency and the limit, but they doesnt work for us, because we get
incoherent values.

We have another question, what is the normal values for dropped and
overlimit?.
We have:
qdisc tbf 110: dev eth1 rate 1Mbit burst 20Kb/8 mpu 0b [0001f400] limit
40Kb lat 190.7ms
 Sent 17542230 bytes 11591 pkts (dropped 36, overlimits 35216)

is this normal?.

Thanks.

Alex Leyva
Gobierno del Distrito Federal
Oficialia Mayor
Comite Ejecutivo de Desarrollo Informatico
Direccion de Nuevas Tecnologias

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

             reply	other threads:[~2002-03-22 18:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-22 18:49 Alex Leyva [this message]
2002-03-28 17:09 ` [LARTC] Determining tbf parameters Kurt Wagner
2002-04-01 16:04 ` Alex Leyva

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-101682297718443@msgid-missing \
    --to=aleyva@pichon.df.gob.mx \
    --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.