Netdev List
 help / color / mirror / Atom feed
From: Simon Horman <simon.horman@netronome.com>
To: David Miller <davem@davemloft.net>
Cc: Jiri Pirko <jiri@mellanox.com>,
	Cong Wang <xiyou.wangcong@gmail.com>,
	Jakub Kicinski <jakub.kicinski@netronome.com>,
	netdev@vger.kernel.org, oss-drivers@netronome.com
Subject: [PATCH net-next 0/6] nfp: flower: tunnel TTL & TOS, and Geneve options set & match support
Date: Tue,  7 Aug 2018 17:35:57 +0200	[thread overview]
Message-ID: <20180807153603.1815-1-simon.horman@netronome.com> (raw)

Hi Dave,

this series contains updates for the TC Flower classifier
and the offload facility for it in the NFP driver.

* Patches 1 & 2: update the NFP driver to allow offload
  of matching and setting tunnel ToS/TTL of flows using the TC Flower
  classifier and tun_key action

* Patches 3 & 4: enhance the flow dissector and TC Flower classifier
  to allow match on Geneve options

* Patch 5 & 6: update the NFP driver to allow offload of
  matching and setting Geneve options of flows using the TC Flower
  classifier and tun_key action


John Hurley (2):
  nfp: flower: set ip tunnel ttl from encap action
  nfp: flower: allow matching on ipv4 UDP tunnel tos and ttl

Pieter Jansen van Vuuren (3):
  net/sched: allow flower to match tunnel options
  nfp: flower: add geneve option push action offload
  nfp: flower: add geneve option match offload

Simon Horman (1):
  flow_dissector: allow dissection of tunnel options from metadata

 drivers/net/ethernet/netronome/nfp/flower/action.c | 139 ++++++++++--
 drivers/net/ethernet/netronome/nfp/flower/cmsg.h   |  33 ++-
 drivers/net/ethernet/netronome/nfp/flower/main.h   |   1 +
 drivers/net/ethernet/netronome/nfp/flower/match.c  |  34 +++
 .../net/ethernet/netronome/nfp/flower/offload.c    |  42 +++-
 include/net/flow_dissector.h                       |  17 ++
 include/uapi/linux/pkt_cls.h                       |  26 +++
 net/core/flow_dissector.c                          |  19 +-
 net/sched/cls_flower.c                             | 244 ++++++++++++++++++++-
 9 files changed, 525 insertions(+), 30 deletions(-)

-- 
2.11.0

             reply	other threads:[~2018-08-07 17:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-07 15:35 Simon Horman [this message]
2018-08-07 15:35 ` [PATCH net-next 1/6] nfp: flower: set ip tunnel ttl from encap action Simon Horman
2018-08-07 15:35 ` [PATCH net-next 2/6] nfp: flower: allow matching on ipv4 UDP tunnel tos and ttl Simon Horman
2018-08-07 17:46   ` Or Gerlitz
2018-08-07 17:59     ` John Hurley
2018-08-07 15:36 ` [PATCH net-next 3/6] flow_dissector: allow dissection of tunnel options from metadata Simon Horman
2018-08-07 15:36 ` [PATCH net-next 4/6] net/sched: allow flower to match tunnel options Simon Horman
2018-08-07 17:44   ` Or Gerlitz
2018-08-07 15:36 ` [PATCH net-next 5/6] nfp: flower: add geneve option push action offload Simon Horman
2018-08-07 15:36 ` [PATCH net-next 6/6] nfp: flower: add geneve option match offload Simon Horman
2018-08-07 19:23 ` [PATCH net-next 0/6] nfp: flower: tunnel TTL & TOS, and Geneve options set & match support David Miller

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=20180807153603.1815-1-simon.horman@netronome.com \
    --to=simon.horman@netronome.com \
    --cc=davem@davemloft.net \
    --cc=jakub.kicinski@netronome.com \
    --cc=jiri@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=oss-drivers@netronome.com \
    --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