From: Simon Horman <simon.horman@netronome.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Jiri Pirko <jiri@resnulli.us>,
Jamal Hadi Salim <jhs@mojatatu.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Dinan Gunawardena <dinan.gunawardena@netronome.com>,
netdev@vger.kernel.org, oss-drivers@netronome.com,
Simon Horman <simon.horman@netronome.com>
Subject: [PATCH/RFC iproute2/net-next 0/3] tc: flower: allow control of tree traversal on packet parse errors
Date: Fri, 28 Apr 2017 14:02:58 +0200 [thread overview]
Message-ID: <20170428120301.16500-1-simon.horman@netronome.com> (raw)
Hi,
this series is intended to allow control how the tree of qdisc, classes and
filters is further traversed if an error is encountered when parsing the
packet in order to match the cls_flower filters at a particular prio.
Please see the changelog of the last patch of this series for a more
detailed description.
Simon Horman (3):
tc: flower: update headers for TCA_FLOWER_KEY_MPLS*
tc: flower: update headers for TCA_FLOWER_HEADER_PARSE_ERR_ACT
tc: flower: allow control of tree traversal on packet parse errors
include/linux/pkt_cls.h | 7 +++++++
man/man8/tc-flower.8 | 29 +++++++++++++++++++++++++++--
tc/f_flower.c | 33 +++++++++++++++++++++++++++++++++
3 files changed, 67 insertions(+), 2 deletions(-)
--
2.12.2.816.g2cccc81164
next reply other threads:[~2017-04-28 12:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 12:02 Simon Horman [this message]
2017-04-28 12:02 ` [PATCH/RFC iproute2/net-next 1/3] tc: flower: update headers for TCA_FLOWER_KEY_MPLS* Simon Horman
2017-04-28 12:03 ` [PATCH/RFC iproute2/net-next 2/3] tc: flower: update headers for TCA_FLOWER_HEADER_PARSE_ERR_ACT Simon Horman
2017-04-28 12:03 ` [PATCH/RFC iproute2/net-next 3/3] tc: flower: allow control of tree traversal on packet parse errors 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=20170428120301.16500-1-simon.horman@netronome.com \
--to=simon.horman@netronome.com \
--cc=dinan.gunawardena@netronome.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.com \
--cc=stephen@networkplumber.org \
--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).