From: Simon Horman <simon.horman@netronome.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Dinan Gunawardena <dinan.gunawardena@netronome.com>,
netdev@vger.kernel.org, oss-drivers@netronome.com,
Simon Horman <simon.horman@netronome.com>
Subject: [PATCH iproute2/net-next 0/7] tc: flower: Masked ICMP match and ND match
Date: Thu, 2 Feb 2017 11:38:33 +0100 [thread overview]
Message-ID: <1486031920-10784-1-git-send-email-simon.horman@netronome.com> (raw)
Hi,
this series have several related parts.
* tc: flower: Update documentation to indicate ARP takes IPv4 prefixes
Enhance documentation for consistency with later documentation changes.
* tc: flower: use correct type when calling flower_icmp_attr_type
Type correction to ICMP code; should not have runtime effect
* tc: flower: provide generic masked u8 parser helper
tc: flower: provide generic masked u8 print helper
Generic parsing and printing of masked u8 options
* tc: flower: support masked ICMP code and type match
Support masking ICMP code and type matches.
Unmasked matching is already supported by iproute2
Masked matching is already supported by the kernel.
This is used by the ND patches
* tc: flower: Add TCA_FLOWER_KEY_ND_*
tc: flower: Support matching on ND
The last two patches are marked as RFC as they support functionality
submitted to but not yet not yet present in the kernel.
Simon Horman (7):
tc: flower: Update documentation to indicate ARP takes IPv4 prefixes
tc: flower: use correct type when calling flower_icmp_attr_type
tc: flower: provide generic masked u8 parser helper
tc: flower: provide generic masked u8 print helper
tc: flower: support masked ICMP code and type match
tc: flower: Add TCA_FLOWER_KEY_ND_*
tc: flower: Support matching on ND
include/linux/pkt_cls.h | 7 ++
man/man8/tc-flower.8 | 58 +++++++++--
tc/f_flower.c | 260 +++++++++++++++++++++++++++++++++++++-----------
3 files changed, 258 insertions(+), 67 deletions(-)
--
2.7.0.rc3.207.g0ac5344
next reply other threads:[~2017-02-02 10:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 10:38 Simon Horman [this message]
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
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=1486031920-10784-1-git-send-email-simon.horman@netronome.com \
--to=simon.horman@netronome.com \
--cc=dinan.gunawardena@netronome.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@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;
as well as URLs for NNTP newsgroup(s).