From: David Miller <davem@davemloft.net>
To: jikos@kernel.org
Cc: daniel@iogearbox.net, dsa@cumulusnetworks.com,
simon.horman@netronome.com, xiyou.wangcong@gmail.com,
eric.dumazet@gmail.com, jhs@mojatatu.com, phil@nwl.cc,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH next-next 0/2] qdisc-hashtable fixes
Date: Thu, 18 Aug 2016 21:19:24 -0700 (PDT) [thread overview]
Message-ID: <20160818.211924.685863058808736843.davem@davemloft.net> (raw)
In-Reply-To: <alpine.LNX.2.00.1608162339050.22028@cbobk.fhfr.pm>
From: Jiri Kosina <jikos@kernel.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.
prev parent reply other threads:[~2016-08-19 4:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 21:52 [PATCH next-next 0/2] qdisc-hashtable fixes Jiri Kosina
2016-08-16 21:52 ` [PATCH 1/2] net: sched: fix handling of singleton qdiscs with qdisc_hash Jiri Kosina
2016-08-16 21:53 ` [PATCH 2/2] net: sched: avoid duplicates in qdisc dump Jiri Kosina
2016-08-19 1:39 ` Cong Wang
2016-08-19 21:48 ` Jiri Kosina
2016-08-19 4:19 ` David Miller [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=20160818.211924.685863058808736843.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=daniel@iogearbox.net \
--cc=dsa@cumulusnetworks.com \
--cc=eric.dumazet@gmail.com \
--cc=jhs@mojatatu.com \
--cc=jikos@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=phil@nwl.cc \
--cc=simon.horman@netronome.com \
--cc=xiyou.wangcong@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).