Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "Sumit Pandya" <sumit@elitecore.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] RED problem !
Date: Wed, 02 Jan 2002 11:37:17 +0000	[thread overview]
Message-ID: <marc-lartc-100997071220130@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100990423626623@msgid-missing>

	Or from my law for implement RED you can go with
# /sbin/tc qdisc add dev <eth0> parent 10:<2000> red max <64000> min 1500 \
limit <64kb> avpkt 1000 burst 20
here,
	parameters in <> are variable and leave rest as it is
	I assume you wana shapping of 64kb
	2000 is id
	parameter to max is (64 * 1000)

-----Original Message-----
From: bert hubert <ahu@ds9a.nl>
To: Arindam Haldar <ahiam@yahoo.com>
Cc: lartc@mailman.ds9a.nl
Subject: Re: [LARTC] RED problem !

On Tue, Jan 01, 2002 at 10:33:06PM +0530, Arindam Haldar wrote:
> hi  all,
> 
> while trying red inplace of sfq/pfifo i go the follwing error
> 
> tc qdisc add dev eth0 parent 1:470 red max 12288 min 6100 limit 12288 
> avpkt 1514 burst 2

This returns -1:

int tc_red_eval_ewma(unsigned qmin, unsigned burst, unsigned avpkt)
{
        int wlog = 1;
        double W = 0.5;
        double a = (double)burst + 1 - (double)qmin/avpkt;

        if (a < 1.0)
                return -1;
        for (wlog=1; wlog<32; wlog++, W /= 2) {
                if (a <= (1 - pow(1-W, burst))/W)
                        return wlog;
        }
        return -1;
}


You can use this to calculate what is wrong. Either burst+1-qmin/avpkt is
smaller than 1, or a is too high to be matched by a time constant.

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

      parent reply	other threads:[~2002-01-02 11:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-01 16:57 [LARTC] RED problem ! Arindam Haldar
2002-01-01 18:58 ` bert hubert
2002-01-02 11:37 ` Sumit Pandya [this message]

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-100997071220130@msgid-missing \
    --to=sumit@elitecore.com \
    --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