From: Eyal Birger <eyal.birger@gmail.com>
To: netdev@vger.kernel.org, pablo@netfilter.org, jhs@mojatatu.com
Cc: coreteam@netfilter.org, shmulik@metanetworks.com,
Eyal Birger <eyal@metanetworks.com>
Subject: [PATCH net-next 0/2] net: sched: Introduce em_policy ematch
Date: Fri, 12 Jan 2018 14:57:23 +0200 [thread overview]
Message-ID: <1515761845-31323-1-git-send-email-eyal.birger@gmail.com> (raw)
From: Eyal Birger <eyal@metanetworks.com>
The following patchset introduces a new tc ematch for matching IPSec
traffic from a tc context.
This allows early classification as well as mirroning/redirecting IPSec
traffic based on decapsulation criteria.
The matching functionality is based on the netfilter xt_policy match, and
shares code and data structures.
Eyal Birger (2):
net: netfilter: export xt_policy match_policy_in() as
xt_policy_match_policy_in()
net: sched: add xfrm policy ematch
include/net/netfilter/xt_policy.h | 12 ++++
include/uapi/linux/pkt_cls.h | 3 +-
net/netfilter/xt_policy.c | 18 +++---
net/sched/Kconfig | 10 ++++
net/sched/Makefile | 1 +
net/sched/em_policy.c | 117 ++++++++++++++++++++++++++++++++++++++
6 files changed, 152 insertions(+), 9 deletions(-)
create mode 100644 include/net/netfilter/xt_policy.h
create mode 100644 net/sched/em_policy.c
--
2.7.4
next reply other threads:[~2018-01-12 12:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 12:57 Eyal Birger [this message]
2018-01-12 12:57 ` [PATCH net-next 1/2] net: netfilter: export xt_policy match_policy_in() as xt_policy_match_policy_in() Eyal Birger
2018-01-12 13:41 ` Pablo Neira Ayuso
2018-01-12 13:56 ` Eyal Birger
2018-01-12 14:00 ` Pablo Neira Ayuso
2018-01-14 12:47 ` Eyal Birger
2018-01-15 10:57 ` Pablo Neira Ayuso
2018-01-15 11:48 ` Eyal Birger
2018-02-14 8:14 ` Eyal Birger
2018-02-14 10:19 ` Pablo Neira Ayuso
2018-02-15 17:47 ` Eyal Birger
2018-01-12 12:57 ` [PATCH net-next 2/2] net: sched: add xfrm policy ematch Eyal Birger
2018-01-16 6:30 ` Cong Wang
2018-01-16 18:17 ` Eyal Birger
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=1515761845-31323-1-git-send-email-eyal.birger@gmail.com \
--to=eyal.birger@gmail.com \
--cc=coreteam@netfilter.org \
--cc=eyal@metanetworks.com \
--cc=jhs@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=shmulik@metanetworks.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).