public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Simon Horman <simon.horman@netronome.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
	Dinan Gunawardena <dinan.gunawardena@netronome.com>,
	netdev@vger.kernel.org, oss-drivers@netronome.com
Subject: Re: [PATCH iproute2/net-next 7/7] tc: flower: Support matching on ND
Date: Mon, 6 Feb 2017 10:44:59 +0100	[thread overview]
Message-ID: <20170206094459.GA2024@nanopsycho> (raw)
In-Reply-To: <20170206084359.GA20384@penelope.horms.nl>

Mon, Feb 06, 2017 at 09:44:00AM CET, simon.horman@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.horman@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.horman@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.

Then mark it "RFC".


>
>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.

  reply	other threads:[~2017-02-06  9:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-02 10:38 [PATCH iproute2/net-next 0/7] tc: flower: Masked ICMP match and ND match Simon Horman
2017-02-02 10:38 ` [PATCH iproute2/net-next 1/7] tc: flower: Update documentation to indicate ARP takes IPv4 prefixes Simon Horman
2017-02-02 10:38 ` [PATCH iproute2/net-next 2/7] tc: flower: use correct type when calling flower_icmp_attr_type Simon Horman
2017-02-02 10:38 ` [PATCH iproute2/net-next 3/7] tc: flower: provide generic masked u8 parser helper Simon Horman
2017-02-02 10:38 ` [PATCH iproute2/net-next 4/7] tc: flower: provide generic masked u8 print helper Simon Horman
2017-02-02 10:38 ` [PATCH iproute2/net-next 5/7] tc: flower: support masked ICMP code and type match Simon Horman
2017-02-02 10:38 ` [PATCH iproute2/net-next 6/7] tc: flower: Add TCA_FLOWER_KEY_ND_* Simon Horman
2017-02-02 10:38 ` [PATCH iproute2/net-next 7/7] tc: flower: Support matching on ND Simon Horman
2017-02-02 17:27   ` Jiri Pirko
2017-02-06  8:44     ` Simon Horman
2017-02-06  9:44       ` Jiri Pirko [this message]
2017-02-06 10:09         ` [oss-drivers] " Simon Horman
2017-02-07 16:50       ` Stephen Hemminger
2017-02-06 22:28 ` [PATCH iproute2/net-next 0/7] tc: flower: Masked ICMP match and ND match Stephen Hemminger
2017-02-07  7:52   ` Simon Horman

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=20170206094459.GA2024@nanopsycho \
    --to=jiri@resnulli.us \
    --cc=dinan.gunawardena@netronome.com \
    --cc=netdev@vger.kernel.org \
    --cc=oss-drivers@netronome.com \
    --cc=simon.horman@netronome.com \
    --cc=stephen@networkplumber.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox