From: Denys Fedorysychenko <nuclearcat@nuclearcat•com>
To: Patrick McHardy <kaber@trash•net>
Cc: netdev@vger•kernel.org, Jeff Garzik <jeff@garzik•org>,
Eric Dumazet <eric.dumazet@gmail•com>
Subject: Re: HFSC classes going out of bounds, regression in recent kernels?
Date: Sun, 11 Apr 2010 05:10:06 +0300 [thread overview]
Message-ID: <201004110510.06162.nuclearcat@nuclearcat.com> (raw)
In-Reply-To: <4BBB5543.40607@trash.net>
On Tuesday 06 April 2010 18:37:39 Patrick McHardy wrote:
> Denys Fedorysychenko wrote:
> > I notice on one of my QoS machines that HFSC start going out of bandwidth
> > limits. The most terrible thing - it happens suddenly, and if i just
> > relaunch QoS script - everything will work fine.
>
> That sounds like there's an overflow somewhere.
>
> > I'm not sure it is not my mistake, but most probably it is a bug.
> > I can't tell for sure when it is happened, last kernel was on this
> > machine 2.6.28 i guess, or maybe even older.
>
> Looking through the recent patches in this area, my prime suspect
> is the attached patch. Does reverting it make any difference?
>
Hi, i made sure - bug not related to this patch. I try to patch (also had to
test latest stable release, to make sure it is appearing on it), and each test
taking 1 day. If i "restart" script to resetup HFSC - it works for a while
fine. At next day, peak time period - it goes wild.
There is another thing also, i am going to try now, old kernel was 64-bit, but
now 32bit, so i will try to shift to 64bit again.
It can be not regression, but a bug. I guess not many people use HFSC, even it
is definitely better than HTB. Or i'm wrong?
next prev parent reply other threads:[~2010-04-11 2:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 15:22 HFSC classes going out of bounds, regression in recent kernels? Denys Fedorysychenko
2010-04-06 15:37 ` Patrick McHardy
2010-04-06 15:45 ` Denys Fedorysychenko
2010-04-11 2:10 ` Denys Fedorysychenko [this message]
2010-05-20 1:34 ` Denys Fedorysychenko
2010-05-31 17:53 ` Michal Soltys
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=201004110510.06162.nuclearcat@nuclearcat.com \
--to=nuclearcat@nuclearcat$(echo .)com \
--cc=eric.dumazet@gmail$(echo .)com \
--cc=jeff@garzik$(echo .)org \
--cc=kaber@trash$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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