ice: GTP support in switchdev
Subsystems (5)
RFC PATCH v3 4/5 ice: Fix FV offset searching
In reply to Marcin SzycikFrom: Michal Swiatkowski <[email protected]>
Checking only protocol ids while searching for correct FVs can lead to a situation, when incorrect FV will be added to the list. Incorrect means that FV has correct protocol id but incorrect offset.
Call ice_get_sw_fv_list with ice_prot_lkup_ext struct which contains all protocol ids with offsets.
With this modification allocating and collecting protocol ids list is not longer needed.
--- .../net/ethernet/intel/ice/ice_flex_pipe.c | 16 +++----- .../net/ethernet/intel/ice/ice_flex_pipe.h | 2 +- drivers/net/ethernet/intel/ice/ice_switch.c | 39 +------------------ 3 files changed, 9 insertions(+), 48 deletions(-)
drivers/net/ethernet/intel/ice/ice_flex_pipe.c +6 -10
@@ -1781,7 +1781,7 @@ ice_get_sw_fv_bitmap(struct ice_hw *hw, enum ice_prof_type req_profs,* allocated for every list entry. */ int -ice_get_sw_fv_list (struct ice_hw *hw,u8 *prot_ids,u16 ids_cnt, +ice_get_sw_fv_list (struct ice_hw *hw,struct ice_prot_lkup_ext *lkups,unsigned long *bm,struct list_head *fv_list) {struct ice_sw_fv_list_entry *fvl;
@@ -1793,7 +1793,7 @@ ice_get_sw_fv_list(struct ice_hw *hw, u8 *prot_ids, u16 ids_cnt,memset (&state,0 ,sizeof (state)); -if (!ids_cnt || !hw->seg) +if (!lkups->n_val_words || !hw->seg)return -EINVAL ; ice_seg = hw->seg;
@@ -1812,20 +1812,16 @@ ice_get_sw_fv_list(struct ice_hw *hw, u8 *prot_ids, u16 ids_cnt,if (!test_bit ((u16 )offset, bm))continue ; -for (i =0 ; i < ids_cnt; i++) { +for (i =0 ; i < lkups->n_val_words; i++) {int j; -/* This code assumes that if a switch field vector line -* has a matching protocol, then this line will contain -* the entries necessary to represent every field in -* that protocol header. -*/ for (j =0 ; j < hw->blk[ICE_BLK_SW ].es.fvw; j++) -if (fv->ew[j].prot_id == prot_ids[i]) +if (fv->ew[j].prot_id == lkups->fv_words[i].prot_id && + fv->ew[j].off == lkups->fv_words[i].off)break ;if (j >= hw->blk[ICE_BLK_SW ].es.fvw)break ; -if (i +1 == ids_cnt) { +if (i +1 == lkups->n_val_words) { fvl =devm_kzalloc (ice_hw_to_dev (hw),sizeof (*fvl),GFP_KERNEL );if (!fvl)
drivers/net/ethernet/intel/ice/ice_flex_pipe.h +1 -1
@@ -87,7 +87,7 @@ ice_get_sw_fv_bitmap(struct ice_hw *hw, enum ice_prof_type type,void ice_init_prof_result_bm (struct ice_hw *hw);int -ice_get_sw_fv_list (struct ice_hw *hw,u8 *prot_ids,u16 ids_cnt, +ice_get_sw_fv_list (struct ice_hw *hw,struct ice_prot_lkup_ext *lkups,unsigned long *bm,struct list_head *fv_list); bool ice_get_open_tunnel_port(struct ice_hw *hw, u16 *port,
drivers/net/ethernet/intel/ice/ice_switch.c +2 -37
@@ -4426,41 +4426,6 @@ ice_create_recipe_group(struct ice_hw *hw, struct ice_sw_recipe *rm,return status; } -/** -* ice_get_fv - get field vectors/extraction sequences for spec. lookup types -* @hw: pointer to hardware structure -* @lkups: lookup elements or match criteria for the advanced recipe, one -* structure per protocol header -* @lkups_cnt: number of protocols -* @bm: bitmap of field vectors to consider -* @fv_list: pointer to a list that holds the returned field vectors -*/ -static int -ice_get_fv (struct ice_hw *hw,struct ice_adv_lkup_elem *lkups,u16 lkups_cnt, -unsigned long *bm,struct list_head *fv_list) -{ -u8 *prot_ids; -int status; -u16 i; - - prot_ids =kcalloc (lkups_cnt,sizeof (*prot_ids),GFP_KERNEL ); -if (!prot_ids) -return -ENOMEM ; - -for (i =0 ; i < lkups_cnt; i++) -if (!ice_prot_type_to_id (lkups[i].type, &prot_ids[i])) { - status = -EIO ; - goto free_mem; - } - -/* Find field vectors that include all specified protocol types */ - status =ice_get_sw_fv_list (hw, prot_ids, lkups_cnt, bm, fv_list); - -free_mem: -kfree (prot_ids); -return status; -} -/** * ice_tun_type_match_word - determine if tun type needs a match mask * @tun_type: tunnel type
@@ -4608,11 +4573,11 @@ ice_add_adv_recipe(struct ice_hw *hw, struct ice_adv_lkup_elem *lkups,/* Get bitmap of field vectors (profiles) that are compatible with the * rule request; only these will be searched in the subsequent call to -* ice_get_fv. +* ice_get_sw_fv_list. */ ice_get_compat_fv_bitmap (hw, rinfo, fv_bitmap); - status =ice_get_fv (hw, lkups, lkups_cnt, fv_bitmap, &rm->fv_list); + status =ice_get_sw_fv_list (hw, lkup_exts, fv_bitmap, &rm->fv_list);if (status) goto err_unroll;
Signature · 1 line
2.31.1
RFC PATCH v3 5/5 ice: Support GTP-U and GTP-C offload in switchdev
In reply to Marcin SzycikAdd support for creating filters for GTP-U and GTP-C in switchdev mode. Add support for parsing GTP-specific options (QFI and PDU type) and TEID.
By default, a filter for GTP-U will be added. To add a filter for GTP-C, specify enc_dst_port = 2123, e.g.:
tc filter add dev $GTP0 ingress prio 1 flower enc_key_id 1337 \enc_dst_port 2123 action mirred egress redirect dev $VF1_PR
Note: IPv6 offload is not supported yet.
Note: GTP-U with no payload offload is not supported yet.
--- drivers/net/ethernet/intel/ice/ice.h | 1 + .../net/ethernet/intel/ice/ice_flex_pipe.c | 30 +- .../net/ethernet/intel/ice/ice_flex_type.h | 6 +- .../ethernet/intel/ice/ice_protocol_type.h | 19 + drivers/net/ethernet/intel/ice/ice_switch.c | 591 +++++++++++++++++- drivers/net/ethernet/intel/ice/ice_switch.h | 9 + drivers/net/ethernet/intel/ice/ice_tc_lib.c | 105 +++- drivers/net/ethernet/intel/ice/ice_tc_lib.h | 3 + 8 files changed, 746 insertions(+), 18 deletions(-)
drivers/net/ethernet/intel/ice/ice.h +1 -0
@@ -51,6 +51,7 @@#include <net/gre.h> #include <net/udp_tunnel.h> #include <net/vxlan.h> +#include <net/gtp.h> #if IS_ENABLED (CONFIG_DCB )#include <scsi/iscsi_proto.h> #endif /* CONFIG_DCB */
drivers/net/ethernet/intel/ice/ice_flex_pipe.c +28 -2
@@ -1701,16 +1701,42 @@ static struct ice_buf_build *ice_pkg_buf_alloc(struct ice_hw *hw)return bld; } +static bool ice_is_gtp_u_profile (u16 prof_idx) +{ +return (prof_idx >=ICE_PROFID_IPV6_GTPU_TEID && + prof_idx <=ICE_PROFID_IPV6_GTPU_IPV6_TCP_INNER ) || + prof_idx ==ICE_PROFID_IPV4_GTPU_TEID ; +} + +static bool ice_is_gtp_c_profile (u16 prof_idx) +{ +switch (prof_idx) { +case ICE_PROFID_IPV4_GTPC_TEID : +case ICE_PROFID_IPV4_GTPC_NO_TEID : +case ICE_PROFID_IPV6_GTPC_TEID : +case ICE_PROFID_IPV6_GTPC_NO_TEID : +return true; +default : +return false; + } +} +/** * ice_get_sw_prof_type - determine switch profile type * @hw: pointer to the HW structure * @fv: pointer to the switch field vector */ static enum ice_prof_type -ice_get_sw_prof_type (struct ice_hw *hw,struct ice_fv *fv) +ice_get_sw_prof_type (struct ice_hw *hw,struct ice_fv *fv,u32 prof_idx) {u16 i; +if (ice_is_gtp_c_profile (prof_idx)) +return ICE_PROF_TUN_GTPC ; + +if (ice_is_gtp_u_profile (prof_idx)) +return ICE_PROF_TUN_GTPU ; +for (i =0 ; i < hw->blk[ICE_BLK_SW ].es.fvw; i++) {/* UDP tunnel will have UDP_OF protocol ID and VNI offset */ if (fv->ew[i].prot_id == (u8)ICE_PROT_UDP_OF &&
@@ -1757,7 +1783,7 @@ ice_get_sw_fv_bitmap(struct ice_hw *hw, enum ice_prof_type req_profs,if (fv) {/* Determine field vector type */ - prof_type =ice_get_sw_prof_type (hw, fv); + prof_type =ice_get_sw_prof_type (hw, fv, offset);if (req_profs & prof_type)set_bit ((u16 )offset, bm);
drivers/net/ethernet/intel/ice/ice_flex_type.h +5 -1
@@ -416,6 +416,8 @@ enum ice_tunnel_type {TNL_VXLAN =0 ,TNL_GENEVE ,TNL_GRETAP , +TNL_GTPC , +TNL_GTPU , __TNL_TYPE_CNT,TNL_LAST =0xFF , TNL_ALL = 0xFF,
@@ -659,7 +661,9 @@ enum ice_prof_type {ICE_PROF_NON_TUN =0x1 ,ICE_PROF_TUN_UDP =0x2 ,ICE_PROF_TUN_GRE =0x4 , -ICE_PROF_TUN_ALL =0x6 , +ICE_PROF_TUN_GTPU =0x8 , +ICE_PROF_TUN_GTPC =0x10 , +ICE_PROF_TUN_ALL =0x1E , ICE_PROF_ALL = 0xFF, };#endif /* _ICE_FLEX_TYPE_H_ */
drivers/net/ethernet/intel/ice/ice_protocol_type.h +19 -0
@@ -40,6 +40,8 @@ enum ice_protocol_type {ICE_VXLAN ,ICE_GENEVE ,ICE_NVGRE , +ICE_GTP , +ICE_GTP_NO_PAY ,ICE_VXLAN_GPE ,ICE_SCTP_IL ,ICE_PROTOCOL_LAST
@@ -50,6 +52,8 @@ enum ice_sw_tunnel_type {ICE_SW_TUN_VXLAN ,ICE_SW_TUN_GENEVE ,ICE_SW_TUN_NVGRE , +ICE_SW_TUN_GTPU , +ICE_SW_TUN_GTPC , ICE_ALL_TUNNELS /* All tunnel types including NVGRE */ };
@@ -179,6 +183,20 @@ struct ice_udp_tnl_hdr {__be32 vni;/* only use lower 24-bits */ }; +struct ice_udp_gtp_hdr { +u8 flags; +u8 msg_type; +__be16 rsrvd_len; +__be32 teid; +__be16 rsrvd_seq_nbr; +u8 rsrvd_n_pdu_nbr; +u8 rsrvd_next_ext; +u8 rsvrd_ext_len; +u8 pdu_type; +u8 qfi; +u8 rsvrd; +}; +struct ice_nvgre_hdr {__be16 flags;__be16 protocol;
@@ -195,6 +213,7 @@ union ice_prot_hdr {struct ice_sctp_hdr sctp_hdr;struct ice_udp_tnl_hdr tnl_hdr;struct ice_nvgre_hdr nvgre_hdr; +struct ice_udp_gtp_hdr gtp_hdr; };/* This is mapping table entry that maps every word within a given protocol
drivers/net/ethernet/intel/ice/ice_switch.c +579 -12
672 lines not on this page · raw message
drivers/net/ethernet/intel/ice/ice_switch.h +9 -0
@@ -14,6 +14,15 @@#define ICE_VSI_INVAL_ID 0xffff#define ICE_INVAL_Q_HANDLE 0xFFFF +/* Switch Profile IDs for Profile related switch rules */ +#define ICE_PROFID_IPV4_GTPC_TEID 41 +#define ICE_PROFID_IPV4_GTPC_NO_TEID 42 +#define ICE_PROFID_IPV4_GTPU_TEID 43 +#define ICE_PROFID_IPV6_GTPC_TEID 44 +#define ICE_PROFID_IPV6_GTPC_NO_TEID 45 +#define ICE_PROFID_IPV6_GTPU_TEID 46 +#define ICE_PROFID_IPV6_GTPU_IPV6_TCP_INNER 70 +#define ICE_SW_RULE_RX_TX_NO_HDR_SIZE \ (offsetof(struct ice_aqc_sw_rules_elem, pdata.lkup_tx_rx.hdr))
drivers/net/ethernet/intel/ice/ice_tc_lib.c +102 -3
159 lines not on this page · raw message
drivers/net/ethernet/intel/ice/ice_tc_lib.h +3 -0
@@ -22,6 +22,7 @@#define ICE_TC_FLWR_FIELD_ENC_SRC_L4_PORT BIT(15)#define ICE_TC_FLWR_FIELD_ENC_DST_MAC BIT(16)#define ICE_TC_FLWR_FIELD_ETH_TYPE_ID BIT(17) +#define ICE_TC_FLWR_FIELD_ENC_OPTS BIT(18)#define ICE_TC_FLOWER_MASK_32 0xFFFFFFFF
@@ -119,6 +120,8 @@ struct ice_tc_flower_fltr {struct ice_tc_flower_lyr_2_4_hdrs inner_headers;struct ice_vsi *src_vsi;__be32 tenant_id; +struct gtp_pdu_session_info gtp_pdu_info_keys; +struct gtp_pdu_session_info gtp_pdu_info_masks;u32 flags;u8 tunnel_type;struct ice_tc_flower_action action;
Signature · 1 line
2.31.1
v3 cover ice: GTP support in switchdev
Add support for adding GTP-C and GTP-U filters in switchdev mode.
To create a filter for GTP, create a GTP-type netdev with ip tool, enable hardware offload, add qdisc and add a filter in tc:
ip link add $GTP0 type gtp role <sgsn/ggsn> hsize <hsize> ethtool -K $PF0 hw-tc-offload on
tc qdisc add dev $GTP0 ingress
tc filter add dev $GTP0 ingress prio 1 flower enc_key_id 1337 \
action mirred egress redirect dev $VF1_PR
By default, a filter for GTP-U will be added. To add a filter for GTP-C, specify enc_dst_port = 2123, e.g.:
tc filter add dev $GTP0 ingress prio 1 flower enc_key_id 1337 \enc_dst_port 2123 action mirred egress redirect dev $VF1_PR
Note: IPv6 offload is not supported yet.
Note: GTP-U with no payload offload is not supported yet.
ICE COMMS package is required to create a filter as it contains GTP profiles.
Changes in iproute2 are required to be able to add GTP netdev and use GTP-specific options (QFI and PDU type). This patchset will be submitted separately.
v2: Adding more CC
v3: Fixed mail thread, sorry for spam
Marcin Szycik (1):
ice: Support GTP-U and GTP-C offload in switchdev
Michal Swiatkowski (1):
ice: Fix FV offset searching
Wojciech Drewek (3):
gtp: Allow to create GTP device without FDs
gtp: Add support for checking GTP device type
net/sched: Allow flower to match on GTP options
drivers/net/ethernet/intel/ice/ice.h | 1 + .../net/ethernet/intel/ice/ice_flex_pipe.c | 46 +- .../net/ethernet/intel/ice/ice_flex_pipe.h | 2 +- .../net/ethernet/intel/ice/ice_flex_type.h | 6 +- .../ethernet/intel/ice/ice_protocol_type.h | 19 + drivers/net/ethernet/intel/ice/ice_switch.c | 630 ++++++++++++++++-- drivers/net/ethernet/intel/ice/ice_switch.h | 9 + drivers/net/ethernet/intel/ice/ice_tc_lib.c | 105 ++- drivers/net/ethernet/intel/ice/ice_tc_lib.h | 3 + drivers/net/gtp.c | 74 +- include/net/gtp.h | 11 + include/uapi/linux/if_tunnel.h | 4 +- include/uapi/linux/pkt_cls.h | 15 + net/sched/cls_flower.c | 116 ++++ 14 files changed, 967 insertions(+), 74 deletions(-)
Signature · 1 line
2.31.1
RFC PATCH v3 2/5 gtp: Add support for checking GTP device type
From: Wojciech Drewek <[email protected]>
Add a function that checks if a net device type is GTP.
--- include/net/gtp.h | 6 ++++++ 1 file changed, 6 insertions(+)
include/net/gtp.h +6 -0
@@ -27,6 +27,12 @@ struct gtp1_header { /* According to 3GPP TS 29.060. */__be32 tid; } __attribute__ ((packed)); +static inline bool netif_is_gtp (const struct net_device *dev) +{ +return dev->rtnl_link_ops && + !strcmp (dev->rtnl_link_ops->kind,"gtp" ); +} +#define GTP1_F_NPDU 0x01#define GTP1_F_SEQ 0x02#define GTP1_F_EXTHDR 0x04
Signature · 1 line
2.31.1
RFC PATCH v3 3/5 net/sched: Allow flower to match on GTP options
In reply to Marcin SzycikFrom: Wojciech Drewek <[email protected]>
Options are as follows: PDU_TYPE:QFI and they refernce to the fields from the PDU Session Protocol. PDU Session data is conveyed in GTP-U Extension Header.
GTP-U Extension Header is described in 3GPP TS 29.281. PDU Session Protocol is described in 3GPP TS 38.415.
PDU_TYPE - indicates the type of the PDU Session Information (4 bits)
QFI - QoS Flow Identifier (6 bits)
# ip link add gtp_dev type gtp role sgsn
# tc qdisc add dev gtp_dev ingress
# tc filter add dev gtp_dev protocol ip parent ffff: \
flower \
enc_key_id 11 \
gtp_opts 1:8/ff:ff \
action mirred egress redirect dev eth0--- include/net/gtp.h | 5 ++ include/uapi/linux/if_tunnel.h | 4 +- include/uapi/linux/pkt_cls.h | 15 +++++ net/sched/cls_flower.c | 116 +++++++++++++++++++++++++++++++++ 4 files changed, 139 insertions(+), 1 deletion(-)
include/net/gtp.h +5 -0
@@ -27,6 +27,11 @@ struct gtp1_header { /* According to 3GPP TS 29.060. */__be32 tid; } __attribute__ ((packed)); +struct gtp_pdu_session_info {/* According to 3GPP TS 38.415. */ +u8 pdu_type; +u8 qfi; +}; +static inline bool netif_is_gtp (const struct net_device *dev) { return dev->rtnl_link_ops &&
include/uapi/linux/if_tunnel.h +3 -1
@@ -176,8 +176,10 @@ enum {#define TUNNEL_VXLAN_OPT __cpu_to_be16(0x1000)#define TUNNEL_NOCACHE __cpu_to_be16(0x2000)#define TUNNEL_ERSPAN_OPT __cpu_to_be16(0x4000) +#define TUNNEL_GTP_OPT __cpu_to_be16(0x8000)#define TUNNEL_OPTIONS_PRESENT \ - (TUNNEL_GENEVE_OPT | TUNNEL_VXLAN_OPT | TUNNEL_ERSPAN_OPT) + (TUNNEL_GENEVE_OPT | TUNNEL_VXLAN_OPT | TUNNEL_ERSPAN_OPT | \ + TUNNEL_GTP_OPT)#endif /* _UAPI_IF_TUNNEL_H_ */
include/uapi/linux/pkt_cls.h +15 -0
@@ -616,6 +616,10 @@ enum {* TCA_FLOWER_KEY_ENC_OPT_ERSPAN_ * attributes */ +TCA_FLOWER_KEY_ENC_OPTS_GTP ,/* Nested +* TCA_FLOWER_KEY_ENC_OPT_GTP_ +* attributes +*/ __TCA_FLOWER_KEY_ENC_OPTS_MAX, };
@@ -654,6 +658,17 @@ enum {#define TCA_FLOWER_KEY_ENC_OPT_ERSPAN_MAX \ (__TCA_FLOWER_KEY_ENC_OPT_ERSPAN_MAX - 1) +enum { +TCA_FLOWER_KEY_ENC_OPT_GTP_UNSPEC , +TCA_FLOWER_KEY_ENC_OPT_GTP_PDU_TYPE ,/* u8 */ +TCA_FLOWER_KEY_ENC_OPT_GTP_QFI ,/* u8 */ + + __TCA_FLOWER_KEY_ENC_OPT_GTP_MAX, +}; + +#define TCA_FLOWER_KEY_ENC_OPT_GTP_MAX \ + (__TCA_FLOWER_KEY_ENC_OPT_GTP_MAX - 1) +enum {TCA_FLOWER_KEY_MPLS_OPTS_UNSPEC ,TCA_FLOWER_KEY_MPLS_OPTS_LSE ,
net/sched/cls_flower.c +116 -0
158 lines not on this page · raw message
Signature · 1 line
2.31.1
RFC PATCH v3 1/5 gtp: Allow to create GTP device without FDs
In reply to Marcin SzycikFrom: Wojciech Drewek <[email protected]>
Currently, when the user wants to create GTP device, he has to provide file handles to the sockets created in userspace (IFLA_GTP_FD0, IFLA_GTP_FD1). This behaviour is not ideal, considering the option of adding support for GTP device creation through ip link. Ip link application is not a good place to create such sockets.
This patch allows to create GTP device without providing IFLA_GTP_FD0 and IFLA_GTP_FD1 arguments. If the user does not provide file handles to the sockets, then GTP module takes care of creating UDP sockets by itself. Sockets are created with the commonly known UDP ports used for GTP protocol (GTP0_PORT and GTP1U_PORT). In this case we don't have to provide encap_destroy because no extra deinitialization is needed, everything is covered by udp_tunnel_sock_release.
--- drivers/net/gtp.c | 74 ++++++++++++++++++++++++++++++++++++++++++----- 1 file changed, 67 insertions(+), 7 deletions(-)
drivers/net/gtp.c +67 -7
@@ -66,8 +66,10 @@ struct gtp_dev {struct sock *sk0;struct sock *sk1u; +u8 sk_created;struct net_device *dev; +struct net *net;unsigned int role;unsigned int hash_size;
@@ -320,8 +322,16 @@ static void gtp_encap_disable_sock(struct sock *sk)static void gtp_encap_disable (struct gtp_dev *gtp) { -gtp_encap_disable_sock (gtp->sk0); -gtp_encap_disable_sock (gtp->sk1u); +if (gtp->sk_created) { +udp_tunnel_sock_release (gtp->sk0->sk_socket); +udp_tunnel_sock_release (gtp->sk1u->sk_socket); + gtp->sk_created = false; + gtp->sk0 =NULL ; + gtp->sk1u =NULL ; + }else { +gtp_encap_disable_sock (gtp->sk0); +gtp_encap_disable_sock (gtp->sk1u); + } }/* UDP encapsulation receive handler. See net/ipv4/udp.c.
@@ -664,9 +674,6 @@ static int gtp_newlink(struct net *src_net, struct net_device *dev,struct gtp_net *gn;int hashsize, err; -if (!data[IFLA_GTP_FD0 ] && !data[IFLA_GTP_FD1 ]) -return -EINVAL ; - gtp =netdev_priv (dev);if (!data[IFLA_GTP_PDP_HASHSIZE ]) {
@@ -677,6 +684,8 @@ static int gtp_newlink(struct net *src_net, struct net_device *dev, hashsize =1024 ; } + gtp->net = src_net; + err =gtp_hashtable_new (gtp, hashsize);if (err <0 )return err;
@@ -844,6 +853,38 @@ static struct sock *gtp_encap_enable_socket(int fd, int type,return sk; } +static struct sock *gtp_encap_create_sock (int type,struct gtp_dev *gtp) +{ +struct udp_tunnel_sock_cfg tuncfg = {}; +struct udp_port_cfg udp_conf = { + .local_ip.s_addr =htonl (INADDR_ANY ), + .family =AF_INET , + }; +struct net *net = gtp->net; +struct socket *sock; +int err; + +if (type ==UDP_ENCAP_GTP0 ) + udp_conf.local_udp_port =GTP0_PORT ; +else if (type ==UDP_ENCAP_GTP1U ) + udp_conf.local_udp_port =GTP1U_PORT ; +else +return ERR_PTR (-EINVAL ); + + err =udp_sock_create (net, &udp_conf, &sock); +if (err) +return ERR_PTR (err); + + tuncfg.sk_user_data = gtp; + tuncfg.encap_type = type; + tuncfg.encap_rcv = gtp_encap_recv; + tuncfg.encap_destroy =NULL ; + +setup_udp_tunnel_sock (net, sock, &tuncfg); + +return sock->sk; +} +static int gtp_encap_enable (struct gtp_dev *gtp,struct nlattr *data[]) {struct sock *sk1u =NULL ;
@@ -868,11 +909,30 @@ static int gtp_encap_enable(struct gtp_dev *gtp, struct nlattr *data[]) } } +if (!data[IFLA_GTP_FD0 ] && !data[IFLA_GTP_FD1 ]) { + sk0 =gtp_encap_create_sock (UDP_ENCAP_GTP0 , gtp); +if (IS_ERR (sk0)) +return PTR_ERR (sk0); + + sk1u =gtp_encap_create_sock (UDP_ENCAP_GTP1U , gtp); +if (IS_ERR (sk1u)) { +udp_tunnel_sock_release (sk0->sk_socket); +return PTR_ERR (sk1u); + } + gtp->sk_created = true; + } +if (data[IFLA_GTP_ROLE ]) { role =nla_get_u32 (data[IFLA_GTP_ROLE ]);if (role >GTP_ROLE_SGSN ) { -gtp_encap_disable_sock (sk0); -gtp_encap_disable_sock (sk1u); +if (gtp->sk_created) { +udp_tunnel_sock_release (sk0->sk_socket); +udp_tunnel_sock_release (sk1u->sk_socket); + gtp->sk_created = false; + }else { +gtp_encap_disable_sock (sk0); +gtp_encap_disable_sock (sk1u); + }return -EINVAL ; } }
Signature · 1 line
2.31.1
Re: [RFC PATCH net-next v3 1/5] gtp: Allow to create GTP device without FDs
Hi Marcin, Wojciech,
thanks for the revised patch. In general it looks fine to me.
Do you have a public git tree with your patchset applied? I'm asking as we do have automatic testing in place at https://jenkins.osmocom.org/ where I just need to specify a remote git repo andit will build this kernel and run the test suite.
Some minor remarks below, all not critical, just some thoughts.
It might make sense to mention in the commit log that this patch by itself would create GTP-U without GTP ECHO capabilities, and that a subsequent patch will address this.
Quoted 4 lines
This patch allows to create GTP device without providing
IFLA_GTP_FD0andIFLA_GTP_FD1arguments. If the user does not provide file handles to the sockets, then GTP module takes care of creating UDP sockets by itself.
I'm wondering if we should make this more explicit, i.e. rather than implicitly creating the kernel socket automagically, make this mode explicit upon request by some netlink attribute.
Quoted 3 lines
Sockets are created with the
commonly known UDP ports used for GTP protocol (GTP0_PORTandGTP1U_PORT).
I'm wondering if there are use cases that need to operate on non-standard ports. The current module can be used that way (as the socket is created in user space). If the "kernel socket mode" was requested explicitly via netlink attribute, one could just as well pass along the port number[s] this way.
Signature · 4 lines
- Harald Welte <[email protected]> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)
RE: [RFC PATCH net-next v3 1/5] gtp: Allow to create GTP device without FDs
Hi Harald
Thanks for the response.
Quoted 8 lines
-----Original Message-----
From: Harald Welte <[email protected]>
Sent: sobota, 5 lutego 2022 17:34
To: Marcin Szycik <[email protected]>
Cc: [email protected]; [email protected]; Drewek, Wojciech <[email protected]>; [email protected]; [email protected]; [email protected]; [email protected]
Subject: Re: [RFC PATCH net-next v3 1/5] gtp: Allow to create GTP device without FDs
Quoted 8 lines
Hi Marcin, Wojciech,
thanks for the revised patch. In general it looks fine to me.
Do you have a public git tree with your patchset applied? I'm asking as we do have automatic testing in place at https://jenkins.osmocom.org/ where I just need to specify a remote git repo andit will build this kernel and run the test suite.
For now we don't have such tree. I will see what we can do.
Quoted 6 lines
Some minor remarks below, all not critical, just some thoughts.
It might make sense to mention in the commit log that this patch by itself would create GTP-U without GTP ECHO capabilities, and that a subsequent patch will address this.
Sure, I'll add such comment.
Quoted 9 lines
Quoted 5 lines
This patch allows to create GTP device without providing
IFLA_GTP_FD0andIFLA_GTP_FD1arguments. If the user does not provide file handles to the sockets, then GTP module takes care of creating UDP sockets by itself.I'm wondering if we should make this more explicit, i.e. rather than implicitly creating the kernel socket automagically, make this mode explicit upon request by some netlink attribute.
I agree, it would look cleaner.
Quoted 10 lines
Quoted 4 lines
Sockets are created with the
commonly known UDP ports used for GTP protocol (GTP0_PORTandGTP1U_PORT).I'm wondering if there are use cases that need to operate on non-standard ports. The current module can be used that way (as the socket is created in user space). If the "kernel socket mode" was requested explicitly via netlink attribute, one could just as well pass along the port number[s] this way.
Yes, it is possible to create socket with any port number using FD approach, but gtp module still assumes that ports are 2152 and 3386 at least in tx path (see gtp_push_header). Implementing this shouldn't be hard but is it crucial?
Quoted 6 lines
--
- Harald Welte <[email protected]> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."(ETSI EN 300 175-7 Ch. A6)
Re: [RFC PATCH net-next v3 1/5] gtp: Allow to create GTP device without FDs
In reply to Harald WelteHi Harald,
Sorry for long delay in reply.
Quoted 8 lines · Harald Welte
Hi Marcin, Wojciech,
thanks for the revised patch. In general it looks fine to me.
Do you have a public git tree with your patchset applied? I'm asking as we do have automatic testing in place at https://jenkins.osmocom.org/ where I just need to specify a remote git repo andit will build this kernel and run the test suite.
I've created a public fork with our patchset applied, please see [1].
Quoted 20 lines
Some minor remarks below, all not critical, just some thoughts.
It might make sense to mention in the commit log that this patch by itself would create GTP-U without GTP ECHO capabilities, and that a subsequent patch will address this.
Quoted 4 lines
This patch allows to create GTP device without providing
IFLA_GTP_FD0andIFLA_GTP_FD1arguments. If the user does not provide file handles to the sockets, then GTP module takes care of creating UDP sockets by itself.I'm wondering if we should make this more explicit, i.e. rather than implicitly creating the kernel socket automagically, make this mode explicit upon request by some netlink attribute.
Quoted 3 lines
Sockets are created with the
commonly known UDP ports used for GTP protocol (GTP0_PORTandGTP1U_PORT).
Quoted 6 lines
I'm wondering if there are use cases that need to operate on non-standard ports. The current module can be used that way (as the socket is created in user space). If the "kernel socket mode" was requested explicitly via netlink attribute, one could just as well pass along the port number[s] this way.
Re: [RFC PATCH net-next v3 1/5] gtp: Allow to create GTP device without FDs
In reply to Drewek, WojciechHi Wojciech,
Quoted 1 line · Wojciech
For now we don't have such tree. I will see what we can do.
I would appreciate it, so we can get this tested before it hits net-next.
Quoted 5 lines
Quoted 3 lines
I'm wondering if we should make this more explicit, i.e. rather than implicitly creating the kernel socket automagically, make this mode explicit upon request by some netlink attribute.
I agree, it would look cleaner.
Excellent.
Quoted 10 lines
Quoted 9 lines
Quoted 3 lines
Sockets are created with the
commonly known UDP ports used for GTP protocol (GTP0_PORTandGTP1U_PORT).I'm wondering if there are use cases that need to operate on non-standard ports. The current module can be used that way (as the socket is created in user space). If the "kernel socket mode" was requested explicitly via netlink attribute, one could just as well pass along the port number[s] this way.
Quoted 3 lines
Yes, it is possible to create socket with any port number using FD approach, but gtp module still assumes that ports are 2152 and 3386 at least in tx path (see
gtp_push_header). Implementing this shouldn't be hard but is it crucial?
Not crucial.
Signature · 4 lines
- Harald Welte <[email protected]> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)
Re: [RFC PATCH net-next v3 1/5] gtp: Allow to create GTP device without FDs
In reply to Marcin SzycikHi Marcin,
Quoted 11 lines · Marcin Szycik
Quoted 8 lines · Harald Welte
Hi Marcin, Wojciech,
thanks for the revised patch. In general it looks fine to me.
Do you have a public git tree with your patchset applied? I'm asking as we do have automatic testing in place at https://jenkins.osmocom.org/ where I just need to specify a remote git repo andit will build this kernel and run the test suite.
I've created a public fork with our patchset applied, please see [1].
Thanks, I've triggered a build, let's hope it works out. Results should
be at https://jenkins.osmocom.org/jenkins/job/ttcn3-ggsn-test-kernel-git/20/
and detailed logs at https://jenkins.osmocom.org/jenkins/job/ttcn3-ggsn-test-kernel-git/20/console
The same testsuite executed against master can be seen at
https://jenkins.osmocom.org/jenkins/job/ttcn3-ggsn-test-kernel-latest-torvalds/
[the high amount of test cases failing is due to the lack of IPv6 support in the kernel GTP].
Let's hope your forked repo renders identical test results to upstream!
Regards,
Harald
Signature · 4 lines
- Harald Welte <[email protected]> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)
RE: [RFC PATCH net-next v3 1/5] gtp: Allow to create GTP device without FDs
Quoted 10 lines
-----Original Message-----
From: Harald Welte <[email protected]>
Sent: piątek, 11 lutego 2022 10:12
To: Marcin Szycik <[email protected]>
Cc: [email protected]; [email protected]; Drewek, Wojciech <[email protected]>; [email protected]; [email protected]; [email protected]; [email protected]
Subject: Re: [RFC PATCH net-next v3 1/5] gtp: Allow to create GTP device without FDs
Hi Harald,
Thanks for triggering CI.
Do I see correctly that results for our changes are the same as for master?
Regards,
Wojtek
Quoted 32 lines
Hi Marcin,
Quoted 11 lines · Marcin Szycik
Quoted 8 lines · Harald Welte
Hi Marcin, Wojciech,
thanks for the revised patch. In general it looks fine to me.
Do you have a public git tree with your patchset applied? I'm asking as we do have automatic testing in place at https://jenkins.osmocom.org/ where I just need to specify a remote git repo andit will build this kernel and run the test suite.
I've created a public fork with our patchset applied, please see [1].
Thanks, I've triggered a build, let's hope it works out. Results should
be at https://jenkins.osmocom.org/jenkins/job/ttcn3-ggsn-test-kernel-git/20/
and detailed logs at https://jenkins.osmocom.org/jenkins/job/ttcn3-ggsn-test-kernel-git/20/consoleThe same testsuite executed against master can be seen at
https://jenkins.osmocom.org/jenkins/job/ttcn3-ggsn-test-kernel-latest-torvalds/
[the high amount of test cases failing is due to the lack of IPv6 support in the kernel GTP].Let's hope your forked repo renders identical test results to upstream!
Regards,
Harald
--
- Harald Welte <[email protected]> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."(ETSI EN 300 175-7 Ch. A6)
Harald Welte
maintainerRe: [RFC PATCH net-next v3 1/5] gtp: Allow to create GTP device without FDs
Quoted 2 lines · Wojciech
Thanks for triggering CI.
Do I see correctly that results for our changes are the same as for master?
The results are identical to master/net-next, so all good!
Signature · 4 lines
- Harald Welte <[email protected]> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)