All of lore.kernel.org
 help / color / mirror / Atom feed
From: gypsy <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] RE: Sluggish throughput with htb
Date: Fri, 09 Nov 2007 02:49:08 +0000	[thread overview]
Message-ID: <4733CAA4.15DA81F5@iswest.com> (raw)
In-Reply-To: <BAY119-W2442AA9771E9D3FAD5EC59D68B0@phx.gbl>

Andrew Kraslavsky wrote:
> 
> All,
> 
> Follow up to the problem I reported earlier:
> 
> > I have been using the following as a means of rate limiting
> > access to the Internet via eth0 (which connects to my cable
> > modem) and it was working great with my 2.4.20 kernel:
> >
> > tc qdisc del dev eth0 root
> > tc qdisc add dev eth0 root handle 1: htb default 1
> > tc class add dev eth0 parent 1: classid 1:1 htb rate 486kbit ceil 486kbit
> > tc qdisc add dev eth0 parent 1:1 handle 10: sfq perturb 10
> >
> > However, after recently updating to kernel version 2.6.15,
> > throughput on eth0 has become sluggish and it is only by
> > disabling the above that performance is restored.
> >
> > Also, I see a whole slew of the following messages in my log:
> >
> > qdisc_restart: Empty queue has non zero length 1
> 
> I see negative "tokens" and "ctokens" values listed when I do a "show" on the class of eth0:
> 
> $ tc -s -d class show dev eth0
> 
> class htb 1:1 root leaf 10: prio 0 quantum 6075 rate 486000bit ceil 486000bit burst 2206b/8 mpu 0b overhead 0b cburst 2206b/8 mpu 0b overhead 0b level 0

Why is the quantum so large?  Is this a gigabit NIC?

>  Sent 614100 bytes 578 pkts (dropped 0, overlimits 0)
>  rate 31312bit 3pps backlog 106p

This backlog and the 472 borrowed below are what are causing your
negatives.

>  lended: 472 borrowed: 0 giants: 0
>  tokens: -33271 ctokens: -33271
> 
> Are the "tokens" and "ctokens" values ever supposed to be negative?

Yes.

> If so, what does the negative value mean (e.g. borrowed or lent tokens?).

I don't know.  Read the HTB docs.

  If not, is this indicative of a problem that is at all familiar to
anyone?
> 
> Thanks,
> 
> - Andrew Kraslavsky

My guesses are:
1) The clock used by HTB is too slow.
2) This is a gigabit NIC not correctly set up.
--
gypsy
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      reply	other threads:[~2007-11-09  2:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-08  0:55 [LARTC] RE: Sluggish throughput with htb Andrew Kraslavsky
2007-11-09  2:49 ` gypsy [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=4733CAA4.15DA81F5@iswest.com \
    --to=gypsy@iswest.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 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.