From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] strange htb behaviour
Date: Tue, 07 Jan 2003 22:00:09 +0000 [thread overview]
Message-ID: <marc-lartc-104197700128407@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104183289507606@msgid-missing>
On Monday 06 January 2003 07:01, Tobias Geiger wrote:
> Hello List,
>
> I use HTB in a ~80 users serving router with kernel 2.4.20.
>
> eth0 is the internet interface (half-duplex 1Mbit),
> eth1 the internal interface (100Mbit full duplex)
>
> cause of the fact that the router also serves as a http-proxy (squid) i
> thought setting up the default class on eth1 with the real upload-speed
> (100Mbit) would do the job, i.e. shaping normal stuff to 1Mbit except
> local generated proxy-traffic which should be served with the full
> 100Mbit. All other, forwarded, traffic is marked and so filtered to
> other classes than the default.
> To make it short: It works. when i download s.th. directly from the
> server i get the full bw BUT: all other downloads from the internet
> absolutly break down and don"t regenerate after some time. i have to
> restart the qdiscs! Also i get these strange syslog messages:
>
> Jan 6 06:39:05 Q kernel: htb*c20007 m=2 ty270 cƒ11 pq=0 df@9600
> ql=0 pa=0 f:
> Jan 6 06:39:05 Q kernel: htb*c20008 m=1 t=-59999999 cf950
> pq\x126192148 df\x16359424 ql" pa\x10 f:
> Jan 6 06:39:10 Q kernel: NET: 77 messages suppressed.
> Jan 6 06:39:10 Q kernel: HTB: mindelayP0, report it please !
> Jan 6 06:39:10 Q kernel: htb*g j\x126187316
> Jan 6 06:39:10 Q kernel: htb*r7 m=0
> Jan 6 06:39:10 Q kernel: htb*r6 m=0
>
> later also:
>
> Jan 6 06:40:05 Q kernel: NET: 518 messages suppressed.
> Jan 6 06:40:05 Q kernel: HTB: suspicious delay in wait_tree
> d=-1644459092 cl 008 h=1
> Jan 6 06:40:10 Q kernel: NET: 518 messages suppressed.
> Jan 6 06:40:10 Q kernel: HTB: suspicious delay in wait_tree
> d=-1644459092 cl 008 h=1
>
>
> I can't really imagine what causes this strange behaviour, except
> perhaps the r2q/quantum settings with which i played around a little
> bit, but just because the defaults caused also warning-messages in
> syslog. perhaps these r2q/quantum parameters need tuning ?!
> I'll attach my shell-script so you can look at it yourself,
> thank you very much for any hint.
You are not the first one to notice this. But I have no solution/answer.
Maybe Devik does ?
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-01-07 22:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-06 6:01 [LARTC] strange htb behaviour Tobias Geiger
2003-01-07 22:00 ` Stef Coene [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-104197700128407@msgid-missing \
--to=stef.coene@docum.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox