From: Marcin Szycik <marcin.szycik@linux.intel.com>
To: intel-wired-lan@lists.osuosl.org
Cc: netdev@vger.kernel.org, wojciech.drewek@intel.com,
michal.swiatkowski@linux.intel.com, aleksander.lobakin@intel.com,
davem@davemloft.net, kuba@kernel.org, jiri@resnulli.us,
pabeni@redhat.com, jesse.brandeburg@intel.com,
simon.horman@corigine.com, idosch@nvidia.com,
Marcin Szycik <marcin.szycik@linux.intel.com>
Subject: [PATCH iwl-next v2 0/6] ice: Add PFCP filter support
Date: Wed, 7 Jun 2023 13:26:00 +0200 [thread overview]
Message-ID: <20230607112606.15899-1-marcin.szycik@linux.intel.com> (raw)
Add support for creating PFCP filters in switchdev mode. Add pfcp module
that allows to create a PFCP-type netdev. The netdev then can be passed to
tc when creating a filter to indicate that PFCP filter should be created.
To add a PFCP filter, a special netdev must be created and passed to tc
command:
ip link add pfcp0 type pfcp
tc filter add dev eth0 ingress prio 1 flower pfcp_opts \
1:123/ff:fffffffffffffff0 skip_hw action mirred egress redirect dev pfcp0
Changes in iproute2 are required to be able to add the pfcp netdev and use
pfcp_opts in tc (patchset will be submitted later).
ICE COMMS package is required as it contains PFCP profiles.
Part of this patchset modifies IP_TUNNEL_*_OPTs, which were previously
stored in a __be16. All possible values have already been used, making it
impossible to add new ones.
Alexander Lobakin (2):
ip_tunnel: use a separate struct to store tunnel params in the kernel
ip_tunnel: convert __be16 tunnel flags to bitmaps
Marcin Szycik (2):
ice: refactor ICE_TC_FLWR_FIELD_ENC_OPTS
ice: Add support for PFCP hardware offload in switchdev
Michal Swiatkowski (1):
pfcp: always set pfcp metadata
Wojciech Drewek (1):
pfcp: add PFCP module
drivers/net/Kconfig | 13 +
drivers/net/Makefile | 1 +
drivers/net/bareudp.c | 19 +-
drivers/net/ethernet/intel/ice/ice_ddp.c | 9 +
.../net/ethernet/intel/ice/ice_flex_type.h | 4 +-
.../ethernet/intel/ice/ice_protocol_type.h | 12 +
drivers/net/ethernet/intel/ice/ice_switch.c | 85 +++++
drivers/net/ethernet/intel/ice/ice_switch.h | 2 +
drivers/net/ethernet/intel/ice/ice_tc_lib.c | 68 +++-
drivers/net/ethernet/intel/ice/ice_tc_lib.h | 7 +-
.../ethernet/mellanox/mlx5/core/en/tc_tun.h | 2 +-
.../mellanox/mlx5/core/en/tc_tun_encap.c | 6 +-
.../mellanox/mlx5/core/en/tc_tun_geneve.c | 12 +-
.../mellanox/mlx5/core/en/tc_tun_gre.c | 9 +-
.../mellanox/mlx5/core/en/tc_tun_vxlan.c | 9 +-
.../net/ethernet/mellanox/mlx5/core/en_tc.c | 15 +-
.../ethernet/mellanox/mlxsw/spectrum_ipip.c | 62 ++--
.../ethernet/mellanox/mlxsw/spectrum_ipip.h | 2 +-
.../ethernet/mellanox/mlxsw/spectrum_span.c | 10 +-
.../ethernet/netronome/nfp/flower/action.c | 12 +-
drivers/net/geneve.c | 46 ++-
drivers/net/pfcp.c | 303 ++++++++++++++++++
drivers/net/vxlan/vxlan_core.c | 14 +-
include/linux/netdevice.h | 7 +-
include/net/dst_metadata.h | 10 +-
include/net/flow_dissector.h | 2 +-
include/net/gre.h | 59 ++--
include/net/ip6_tunnel.h | 4 +-
include/net/ip_tunnels.h | 106 +++++-
include/net/pfcp.h | 83 +++++
include/net/udp_tunnel.h | 4 +-
include/uapi/linux/if_tunnel.h | 36 +++
include/uapi/linux/pkt_cls.h | 14 +
net/bridge/br_vlan_tunnel.c | 5 +-
net/core/filter.c | 20 +-
net/core/flow_dissector.c | 12 +-
net/ipv4/fou_bpf.c | 2 +-
net/ipv4/gre_demux.c | 2 +-
net/ipv4/ip_gre.c | 148 +++++----
net/ipv4/ip_tunnel.c | 92 ++++--
net/ipv4/ip_tunnel_core.c | 83 +++--
net/ipv4/ip_vti.c | 43 ++-
net/ipv4/ipip.c | 33 +-
net/ipv4/ipmr.c | 2 +-
net/ipv4/udp_tunnel_core.c | 5 +-
net/ipv6/addrconf.c | 3 +-
net/ipv6/ip6_gre.c | 87 ++---
net/ipv6/ip6_tunnel.c | 14 +-
net/ipv6/sit.c | 47 ++-
net/netfilter/ipvs/ip_vs_core.c | 6 +-
net/netfilter/ipvs/ip_vs_xmit.c | 20 +-
net/netfilter/nft_tunnel.c | 45 +--
net/openvswitch/flow_netlink.c | 55 ++--
net/psample/psample.c | 26 +-
net/sched/act_tunnel_key.c | 39 +--
net/sched/cls_flower.c | 134 +++++++-
56 files changed, 1501 insertions(+), 469 deletions(-)
create mode 100644 drivers/net/pfcp.c
create mode 100644 include/net/pfcp.h
--
2.31.1
next reply other threads:[~2023-06-07 11:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 11:26 Marcin Szycik [this message]
2023-06-07 11:26 ` [PATCH iwl-next v2 1/6] ip_tunnel: use a separate struct to store tunnel params in the kernel Marcin Szycik
2023-06-07 11:26 ` [PATCH iwl-next v2 2/6] ip_tunnel: convert __be16 tunnel flags to bitmaps Marcin Szycik
2023-06-07 11:26 ` [PATCH iwl-next v2 3/6] pfcp: add PFCP module Marcin Szycik
2023-06-07 11:26 ` [PATCH iwl-next v2 4/6] pfcp: always set pfcp metadata Marcin Szycik
2023-06-07 11:26 ` [PATCH iwl-next v2 5/6] ice: refactor ICE_TC_FLWR_FIELD_ENC_OPTS Marcin Szycik
2023-07-03 11:49 ` [Intel-wired-lan] " Buvaneswaran, Sujai
2023-06-07 11:26 ` [PATCH iwl-next v2 6/6] ice: Add support for PFCP hardware offload in switchdev Marcin Szycik
2023-07-03 11:49 ` [Intel-wired-lan] " Buvaneswaran, Sujai
2023-06-14 9:39 ` [PATCH iwl-next v2 0/6] ice: Add PFCP filter support Marcin Szycik
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=20230607112606.15899-1-marcin.szycik@linux.intel.com \
--to=marcin.szycik@linux.intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=davem@davemloft.net \
--cc=idosch@nvidia.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=michal.swiatkowski@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=simon.horman@corigine.com \
--cc=wojciech.drewek@intel.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).