From: Jamal Hadi Salim <jhs@mojatatu.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, daniel@iogearbox.net,
xiyou.wangcong@gmail.com, alexei.starovoitov@gmail.com,
Jamal Hadi Salim <jhs@mojatatu.com>
Subject: [net-next PATCH 0/5] net_sched: Add support for IFE action
Date: Mon, 22 Feb 2016 08:21:39 -0500 [thread overview]
Message-ID: <1456147304-13355-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).
Described in netdev01 paper:
"Distributing Linux Traffic Control Classifier-Action Subsystem"
Authors: Jamal Hadi Salim and Damascene M. Joachimpillai
Allows for incremental updates for new metadatum support.
This patch set includes support for basic skb metadatum
Followup patches will have more examples of metadata
Jamal Hadi Salim (5):
introduce IFE action
Support to encoding decoding skb mark on IFE action
Support to encoding decoding skb prio on IFE action
Support to encoding decoding skb hashid on IFE action
Support to encoding decoding skb queue map on IFE action
include/net/tc_act/tc_ife.h | 60 +++
include/uapi/linux/tc_act/tc_ife.h | 38 ++
net/sched/Kconfig | 32 ++
net/sched/Makefile | 5 +
net/sched/act_ife.c | 865 +++++++++++++++++++++++++++++++++++++
net/sched/act_meta_mark.c | 81 ++++
net/sched/act_meta_qmap.c | 100 +++++
net/sched/act_meta_skbhash.c | 87 ++++
net/sched/act_meta_skbprio.c | 80 ++++
9 files changed, 1348 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_qmap.c
create mode 100644 net/sched/act_meta_skbhash.c
create mode 100644 net/sched/act_meta_skbprio.c
--
1.9.1
next reply other threads:[~2016-02-22 13:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 13:21 Jamal Hadi Salim [this message]
2016-02-22 13:21 ` [net-next PATCH 1/5] introduce IFE action Jamal Hadi Salim
2016-02-22 13:21 ` [net-next PATCH 2/5] Support to encoding decoding skb mark on " Jamal Hadi Salim
2016-02-22 13:21 ` [net-next PATCH 3/5] Support to encoding decoding skb prio " Jamal Hadi Salim
2016-02-22 17:01 ` Daniel Borkmann
2016-02-22 13:21 ` [net-next PATCH 4/5] Support to encoding decoding skb hashid " Jamal Hadi Salim
2016-02-22 16:56 ` Daniel Borkmann
2016-02-22 13:21 ` [net-next PATCH 5/5] Support to encoding decoding skb queue map " Jamal Hadi Salim
2016-02-22 16:59 ` Daniel Borkmann
2016-02-22 21:03 ` John Fastabend
2016-02-23 12:17 ` Jamal Hadi Salim
2016-02-23 19:33 ` John Fastabend
2016-02-22 16:47 ` [net-next PATCH 0/5] net_sched: Add support for " Daniel Borkmann
2016-02-23 12:09 ` Jamal Hadi Salim
2016-02-23 13:20 ` Daniel Borkmann
2016-02-23 14:28 ` Jamal Hadi Salim
2016-02-23 15:34 ` Daniel Borkmann
2016-02-24 12:49 ` Jamal Hadi Salim
2016-02-24 17:48 ` Daniel Borkmann
2016-02-25 12:23 ` Jamal Hadi Salim
2016-02-25 21:34 ` Daniel Borkmann
2016-02-25 22:40 ` Jamal Hadi Salim
2016-02-26 0:03 ` Daniel Borkmann
2016-02-24 17:58 ` Daniel Borkmann
2016-02-25 12:35 ` Jamal Hadi Salim
2016-02-23 7:00 ` Cong Wang
2016-02-23 12:18 ` 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=1456147304-13355-1-git-send-email-jhs@emojatatu.com \
--to=jhs@mojatatu.com \
--cc=alexei.starovoitov@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.