On Mon, 6 Feb 2017 09:44:00 +0100 Simon Horman <simon.hor...@netronome.com> wrote:
> On Thu, Feb 02, 2017 at 06:27:48PM +0100, Jiri Pirko wrote: > > Thu, Feb 02, 2017 at 11:38:40AM CET, simon.hor...@netronome.com wrote: > > >Allow matching on Neighbour Discovery target IP, and source and > > >destination link-layer addresses for neighbour solicitation and > > >advertisement messages. > > > > > >Sample usage: > > > > > >tc qdisc add dev eth0 ingress > > > > > >tc filter add dev eth0 protocol ipv6 parent ffff: flower \ > > > indev eth0 ip_proto icmpv6 type 136 code 0 \ > > > nd_target 2001:470:7eb3:403:201:8eff:fe22:8fea \ > > > nd_tll 00:01:8e:22:8f:ea action drop > > > > > >Signed-off-by: Simon Horman <simon.hor...@netronome.com> > > > > > > Why you are adding this to iproute2? You only poster RFC for kernel. > > > > Please push to kernel first, let it merge, then send iproute2 support. > > Hi Jiri, > > I think there is a value in making the user-space code available in > parallel with the kernel changes to allow testing and so by any interested > parties. The problem is that the ABI is not defined until it makes it into upstream kernel tree. If a set of developers needs tools, then they can keep a temporary fork (which is what the CAKE developers are doing). > If this is not acceptable I'm happy to stop doing so. But in my ideal world > I'd be very happy to see other TC kernel updates accompanied by > implementations their user-space tool counterparts. If you want something in right away resend those patches.
