From: "Hoggins!" <fuckspam@wheres5.com>
To: lartc@vger.kernel.org
Subject: Re: HTB new API ?
Date: Thu, 27 Mar 2014 15:42:52 +0000 [thread overview]
Message-ID: <533446FC.8050409@wheres5.com> (raw)
In-Reply-To: <533434F0.3000608@wheres5.com>
Hello Dave,
I'm sorry, I'm far from a kernel expert.
From what I can tell, it is surely broken in 3.13 : I tested it last night.
I guess it's okay, I'm still running my "own-compiled" 3.10.25, which
has the correct behavior, but I'd really like to have some benefits of
the latest kernels without the downsides of other required features.
I don't know about 3.14, as I'm still waiting for the release candidates
to be over.
Thanks for your quick answer, and sorry for my bad english !
Regards.
Le 27/03/2014 16:37, Dave Taht a écrit :
> On Thu, Mar 27, 2014 at 7:25 AM, Hoggins! <fuckspam@wheres5.com> wrote:
>> Hello everyone,
>>
>> Can someone point me to the release that "broke" TC / HTB behavior ?
>> I confess I'm not able to find any information (changelog, etc.)
>> regarding this change.
> It wasn't just "a" release that broke htb, it was multiple errors compounded.
>
> some of the breakage goes back to 2.6.39, and others were inserted
> around 3.8...
>
>> I currently have 3.10.25 kernel installed, everything works fine.
> 3.10.12 and later had the needed fixes backported.
>
>> But if I use the latest one, my HTB rules don't behave correctly, and my
> If it's broke in 3.13 or 3.14 need to know.
>
>> traffic shaping is not accurate, priorities are not respected, etc.
>>
>> Any ideas ?
>>
>> Thanks in advance.
>> --
>> To unsubscribe from this list: send the line "unsubscribe lartc" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
prev parent reply other threads:[~2014-03-27 15:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 14:25 HTB new API ? Hoggins!
2014-03-27 15:37 ` Dave Taht
2014-03-27 15:42 ` Hoggins! [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=533446FC.8050409@wheres5.com \
--to=fuckspam@wheres5.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.