Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: [LARTC] HTB dequeueing in pairs fixed
Date: Sat, 31 Jan 2004 01:40:03 +0000	[thread overview]
Message-ID: <401B0773.9020005@dsl.pipex.com> (raw)

I posted earlier when I noticed that htb was releasing packets in pairs, 
even though my burst/quantums were 1 pkt.

To fix I set HTB_HYSTERESIS 0 in net/sched/sch_htb.c .

This gives a noticable gain in upstream worst case latency, for me with 
256kbit/s up I used to see +90 sometimes, now it's +45. For the many who 
  have 128 up it should limit them to +90 rather than +180.

Andy.

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

             reply	other threads:[~2004-01-31  1:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-31  1:40 Andy Furniss [this message]
2004-01-31 10:03 ` [LARTC] HTB dequeueing in pairs fixed Stef Coene
2004-01-31 15:16 ` Artūras Šlajus
2004-01-31 17:00 ` Alexander Clouter
2004-01-31 17:44 ` Andy Furniss
2004-02-01  9:26 ` Stef Coene
2004-02-01 10:21 ` Alexander Clouter

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=401B0773.9020005@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