All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Davidson <kiloman@oatmail.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB debug info in kernel log
Date: Thu, 13 Feb 2003 08:48:41 +0000	[thread overview]
Message-ID: <marc-lartc-104512612114979@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104511747608833@msgid-missing>

On Thu, 13 Feb 2003 at 00:41:54, Stef Coene wrote:

> On Thursday 13 February 2003 08:10, Brad Davidson wrote:
> I had the same problem.  I uncomment the DEFINE statement.  But logging there
> numbers, means there is something miss with your htb setup and has nothing to
> do with you asking for statistics.  You can find more info on the homepage of
> htb.  But it's possible that your rates settings are too low.
> 
> Stef

I used htb.init (http://freshmeat.net/projects/htb.init/) to make my rules, so
I'm pretty sure they should be OK.

I'm looking at the code in htb_dump, which appears to be what's called to get
statistics information by the tc application. It looks to me like if you have
debug enabled, as part of the stats collecting routine, it calls htb_debug_dump
regardless of whether or not there's anything wrong with your setup.

There are other circumstances that it prints an error message followed by a
debug dump, but I'm not seeing an error. It just looks to me like debug info is
printed every time a queue is polled for stats info.

If you want to take a look at what I'm talking about, check out line 1211 of
sch_htb.c

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

  parent reply	other threads:[~2003-02-13  8:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-13  6:24 [LARTC] HTB debug info in kernel log Brad Davidson
2003-02-13  7:30 ` Stef Coene
2003-02-13  8:48 ` Brad Davidson [this message]
2003-02-13 17:37 ` Brad Davidson
2003-02-13 18:35 ` Stef Coene
2003-02-13 23:44 ` Brad Davidson

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-104512612114979@msgid-missing \
    --to=kiloman@oatmail.org \
    --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.