From: Jamal Hadi Salim <jhs@mojatatu.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, daniel@iogearbox.net,
xiyou.wangcong@gmail.com, Jamal Hadi Salim <jhs@mojatatu.com>
Subject: [net-next-2.6 v3 0/3] net_sched: Add support for IFE action
Date: Fri, 26 Feb 2016 17:43:22 -0500 [thread overview]
Message-ID: <1456526605-15774-1-git-send-email-jhs@emojatatu.com> (raw)
From: Jamal Hadi Salim <jhs@mojatatu.com>
As agreed at netconf in Seville, here's the patch finally (1 year
was just too long to wait for an ethertype. Now we are just going
have the user configure one).
Described in netdev01 paper:
"Distributing Linux Traffic Control Classifier-Action Subsystem"
Authors: Jamal Hadi Salim and Damascene M. Joachimpillai
The original motivation and deployment of this work was to horizontally
scale packet processing at scope of a chasis or rack. This means one
could take a tc policy and split it across machines connected over
L2. The paper refers to this as "pipeline stage indexing". Other
use cases which evolved out of the original intent include but are
not limited to carrying OAM information, carrying exception handling
metadata, carrying programmed authentication and authorization information,
encapsulating programmed compliance information, service IDs etc.
Read the referenced paper for more details.
The architecture allows for incremental updates for new metadatum support
to cover different use cases.
This patch set includes support for basic skb metadatum.
Followup patches will have more examples of metadata and other features.
v3 changes:
Integrate with the new namespace changes
Remove skbhash and queue mapping metadata (but keep their claim for ids)
Integrate feedback from Cong
Integrate feedback from Daniel
v2 changes:
Remove module option for an upper bound of metadata
Integrate feedback from Cong
Integrate feedback from Daniel
Jamal Hadi Salim (3):
introduce IFE action
Support to encoding decoding skb mark on IFE action
Support to encoding decoding skb prio on IFE action
include/net/tc_act/tc_ife.h | 61 +++
include/uapi/linux/tc_act/tc_ife.h | 38 ++
net/sched/Kconfig | 22 +
net/sched/Makefile | 3 +
net/sched/act_ife.c | 883 +++++++++++++++++++++++++++++++++++++
net/sched/act_meta_mark.c | 79 ++++
net/sched/act_meta_skbprio.c | 76 ++++
7 files changed, 1162 insertions(+)
create mode 100644 include/net/tc_act/tc_ife.h
create mode 100644 include/uapi/linux/tc_act/tc_ife.h
create mode 100644 net/sched/act_ife.c
create mode 100644 net/sched/act_meta_mark.c
create mode 100644 net/sched/act_meta_skbprio.c
--
1.9.1
next reply other threads:[~2016-02-26 22:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 22:43 Jamal Hadi Salim [this message]
2016-02-26 22:43 ` [net-next-2.6 v3 1/3] introduce IFE action Jamal Hadi Salim
2016-02-26 23:49 ` Cong Wang
2016-02-27 12:27 ` Jamal Hadi Salim
2016-02-26 22:43 ` [net-next-2.6 v3 2/3] Support to encoding decoding skb mark on " Jamal Hadi Salim
2016-02-26 22:43 ` [net-next-2.6 v3 3/3] Support to encoding decoding skb prio " Jamal Hadi Salim
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=1456526605-15774-1-git-send-email-jhs@emojatatu.com \
--to=jhs@mojatatu.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.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