From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Hoggins!" Date: Thu, 27 Mar 2014 15:42:52 +0000 Subject: Re: HTB new API ? Message-Id: <533446FC.8050409@wheres5.com> List-Id: References: <533434F0.3000608@wheres5.com> In-Reply-To: <533434F0.3000608@wheres5.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: lartc@vger.kernel.org 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 =E9crit : > On Thu, Mar 27, 2014 at 7:25 AM, Hoggins! 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 compoun= ded. > > 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 > >