[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20160818.211924.685863058808736843.davem@davemloft.net>
Date: Thu, 18 Aug 2016 21:19:24 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: jikos@...nel.org
Cc: daniel@...earbox.net, dsa@...ulusnetworks.com,
simon.horman@...ronome.com, xiyou.wangcong@...il.com,
eric.dumazet@...il.com, jhs@...atatu.com, phil@....cc,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH next-next 0/2] qdisc-hashtable fixes
From: Jiri Kosina <jikos@...nel.org>
Date: Tue, 16 Aug 2016 23:52:08 +0200 (CEST)
> The following two patches fix all the issues that have been reported
> against the conversion of qdisc linked list to hashtable (currently in
> net-next) so far.
>
> First patch adjusts handling of singleton qdiscs to the new semantics, and
> is rather straightforward.
>
> The second patch, which fixes "cosmetic" issue of duplicate entries in the
> qdisc dump for ingress qdiscs, is a little bit more hairy; I personally
> would love to see all the already existing "if (ingress)"-like hacks go
> away (by, let's say, introducing a general TCQ_F_? flag), but that's way
> out of scope of this patchset (but already on my todo).
>
> Thanks a lot to Daniel Borkmann and David Ahern for reporting the issues
> and testing the patches promptly.
Series applied, thanks Jiri.
Powered by blists - more mailing lists