From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] What determines DROP versus delay ("BACKLOG")?
Date: Sun, 14 Nov 2004 02:12:24 +0000 [thread overview]
Message-ID: <4196BF08.7020100@dsl.pipex.com> (raw)
In-Reply-To: <418D2AA6.68F2871C@iswest.com>
gypsy wrote:
> HTB:
>
> class htb 1:40 parent 1:1 leaf 40: prio 3 rate 358Kbit ceil 529Kbit \
> burst 6Kb cburst 2260b
> Sent 145871726 bytes 97293 pkts (dropped 69, overlimits 0)
> rate 56741bit 37pps backlog 23p
> lended: 77429 borrowed: 19841 giants: 0
>
> I would like to increase "backlog" because I think that would decrease
> "dropped". 23 packets of 1500 bytes each is only 34,500 bytes. IMO,
> there could be up to 64K bytes.
>
> 1) What determines backlog?
> 2) How can it be altered?
If you add a queue say bfifo - you can choose the length.
> 3) Am I on the right track here?
>
> gypsy
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-11-14 2:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-06 19:48 [LARTC] What determines DROP versus delay ("BACKLOG")? gypsy
2004-11-13 17:00 ` Stef Coene
2004-11-14 2:12 ` Andy Furniss [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=4196BF08.7020100@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.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