flow_offload hardware priority fixes
Subsystems (11)
Pablo Neira Ayuso
maintainerv5 cover flow_offload hardware priority fixes
Hi,
This patchset contains two updates for the flow_offload users:
1) Pass the major tc priority to drivers so they do not have to lshift it. This is a preparation patch for the fix coming in patch #2.
2) Set the hardware priority from the netfilter basechain priority, some drivers break when using the existing hardware priority number that is set to zero.
v5: fix patch 2/2 to address a clang warning and to simplify
the priority mapping.
Please, apply.
Pablo Neira Ayuso (2):
net: sched: use major priority number as hardware priority
netfilter: nf_tables: map basechain priority to hardware priority
drivers/net/ethernet/mellanox/mlx5/core/en_tc.c | 2 +- drivers/net/ethernet/mellanox/mlxsw/spectrum_acl.c | 2 +- drivers/net/ethernet/mscc/ocelot_flower.c | 12 +++--------- drivers/net/ethernet/netronome/nfp/flower/qos_conf.c | 2 +- drivers/net/ethernet/stmicro/stmmac/stmmac_tc.c | 2 +- include/net/netfilter/nf_tables_offload.h | 2 ++ include/net/pkt_cls.h | 2 +- net/netfilter/nf_tables_api.c | 4 ++++ net/netfilter/nf_tables_offload.c | 17 ++++++++++++++--- 9 files changed, 28 insertions(+), 17 deletions(-)
Signature · 1 line
2.11.0
Pablo Neira Ayuso
maintainerPATCH v5 1/2 net: sched: use major priority number as hardware priority
tc transparently maps the software priority number to hardware. Update it to pass the major priority which is what most drivers expect. Update drivers too so they do not need to lshift the priority field of the flow_cls_common_offload object. The stmmac driver is an exception, since this code assumes the tc software priority is fine, therefore, lshift it just to be conservative.
---
v5: no changes.
drivers/net/ethernet/mellanox/mlx5/core/en_tc.c | 2 +- drivers/net/ethernet/mellanox/mlxsw/spectrum_acl.c | 2 +- drivers/net/ethernet/mscc/ocelot_flower.c | 12 +++--------- drivers/net/ethernet/netronome/nfp/flower/qos_conf.c | 2 +- drivers/net/ethernet/stmicro/stmmac/stmmac_tc.c | 2 +- include/net/pkt_cls.h | 2 +- 6 files changed, 8 insertions(+), 14 deletions(-)
drivers/net/ethernet/mellanox/mlx5/core/en_tc.c +1 -1
@@ -3167,7 +3167,7 @@ mlx5e_flow_esw_attr_init(struct mlx5_esw_flow_attr *esw_attr, esw_attr->parse_attr = parse_attr; esw_attr->chain = f->common.chain_index; - esw_attr->prio =TC_H_MAJ (f->common.prio) >>16 ; + esw_attr->prio = f->common.prio; esw_attr->in_rep = in_rep; esw_attr->in_mdev = in_mdev;
drivers/net/ethernet/mellanox/mlxsw/spectrum_acl.c +1 -1
@@ -471,7 +471,7 @@ int mlxsw_sp_acl_rulei_commit(struct mlxsw_sp_acl_rule_info *rulei)void mlxsw_sp_acl_rulei_priority (struct mlxsw_sp_acl_rule_info *rulei,unsigned int priority) { - rulei->priority = priority >>16 ; + rulei->priority = priority; } void mlxsw_sp_acl_rulei_keymask_u32(struct mlxsw_sp_acl_rule_info *rulei,
drivers/net/ethernet/mscc/ocelot_flower.c +3 -9
@@ -13,12 +13,6 @@ struct ocelot_port_block {struct ocelot_port *port; }; -static u16 get_prio (u32 prio) -{ -/* prio starts from 0x1000 while the ids starts from 0 */ -return prio >>16 ; -} -static int ocelot_flower_parse_action (struct flow_cls_offload *f,struct ocelot_ace_rule *rule) {
@@ -168,7 +162,7 @@ static int ocelot_flower_parse(struct flow_cls_offload *f, } finished_key_parsing: - ocelot_rule->prio =get_prio (f->common.prio); + ocelot_rule->prio = f->common.prio; ocelot_rule->id = f->cookie;return ocelot_flower_parse_action (f, ocelot_rule); }
@@ -218,7 +212,7 @@ static int ocelot_flower_destroy(struct flow_cls_offload *f,struct ocelot_ace_rule rule;int ret; - rule.prio =get_prio (f->common.prio); + rule.prio = f->common.prio; rule.port = port_block->port; rule.id = f->cookie;
@@ -236,7 +230,7 @@ static int ocelot_flower_stats_update(struct flow_cls_offload *f,struct ocelot_ace_rule rule;int ret; - rule.prio =get_prio (f->common.prio); + rule.prio = f->common.prio; rule.port = port_block->port; rule.id = f->cookie; ret =ocelot_ace_rule_stats_update (&rule);
drivers/net/ethernet/netronome/nfp/flower/qos_conf.c +1 -1
@@ -93,7 +93,7 @@ nfp_flower_install_rate_limiter(struct nfp_app *app, struct net_device *netdev,return -EOPNOTSUPP ; } -if (flow->common.prio != (1 <<16 )) { +if (flow->common.prio !=1 ) {NL_SET_ERR_MSG_MOD (extack,"unsupported offload: qos rate limit offload requires highest priority" );return -EOPNOTSUPP ; }
drivers/net/ethernet/stmicro/stmmac/stmmac_tc.c +1 -1
@@ -94,7 +94,7 @@ static int tc_fill_entry(struct stmmac_priv *priv,struct stmmac_tc_entry *entry, *frag =NULL ;struct tc_u32_sel *sel = cls->knode.sel;u32 off, data, mask, real_off, rem; -u32 prio = cls->common.prio; +u32 prio = cls->common.prio <<16 ;int ret;/* Only 1 match per entry */
include/net/pkt_cls.h +1 -1
@@ -646,7 +646,7 @@ tc_cls_common_offload_init(struct flow_cls_common_offload *cls_common, { cls_common->chain_index = tp->chain->index; cls_common->protocol = tp->protocol; - cls_common->prio = tp->prio; + cls_common->prio = tp->prio >>16 ;if (tc_skip_sw (flags) || flags &TCA_CLS_FLAGS_VERBOSE ) cls_common->extack = extack; }
Signature · 1 line
2.11.0
Pablo Neira Ayuso
maintainerPATCH v5 2/2 netfilter: nf_tables: map basechain priority to hardware priority
In reply to Pablo Neira AyusoThis patch adds initial support for offloading basechains using the priority range from 1 to 65535. This is restricting the netfilter priority range to 16-bit integer since this is what most drivers assume so far from tc. It should be possible to extend this range of supported priorities later on once drivers are updated to support for 32-bit integer priorities.
---
v5: fix clang warning by simplifying the mapping of hardware priorities
to basechain priority in the range of 1-65535. Zero is left behind since some drivers do not support this, no negative basechain priorities are used at this stage.
include/net/netfilter/nf_tables_offload.h | 2 ++ net/netfilter/nf_tables_api.c | 4 ++++ net/netfilter/nf_tables_offload.c | 17 ++++++++++++++--- 3 files changed, 20 insertions(+), 3 deletions(-)
include/net/netfilter/nf_tables_offload.h +2 -0
@@ -73,4 +73,6 @@ int nft_flow_rule_offload_commit(struct net *net); (__reg)->key = __key; \memset (&(__reg)->mask,0xff , (__reg)->len); +int nft_chain_offload_priority (struct nft_base_chain *basechain); +#endif
net/netfilter/nf_tables_api.c +4 -0
@@ -1662,6 +1662,10 @@ static int nf_tables_addchain(struct nft_ctx *ctx, u8 family, u8 genmask, chain->flags |=NFT_BASE_CHAIN | flags; basechain->policy =NF_ACCEPT ; +if (chain->flags &NFT_CHAIN_HW_OFFLOAD && +nft_chain_offload_priority (basechain) <0 ) +return -EOPNOTSUPP ; +flow_block_init (&basechain->flow_block); }else { chain =kzalloc (sizeof (*chain),GFP_KERNEL );
net/netfilter/nf_tables_offload.c +14 -3
@@ -103,10 +103,11 @@ void nft_offload_update_dependency(struct nft_offload_ctx *ctx, }static void nft_flow_offload_common_init (struct flow_cls_common_offload *common, -__be16 proto, -struct netlink_ext_ack *extack) +__be16 proto,int priority, +struct netlink_ext_ack *extack) { common->protocol = proto; + common->prio = priority; common->extack = extack; }
@@ -124,6 +125,15 @@ static int nft_setup_cb_call(struct nft_base_chain *basechain,return 0 ; } +int nft_chain_offload_priority (struct nft_base_chain *basechain) +{ +if (basechain->ops.priority <=0 || + basechain->ops.priority >USHRT_MAX ) +return -1 ; + +return 0 ; +} +static int nft_flow_offload_rule (struct nft_trans *trans,enum flow_cls_command command) {
@@ -142,7 +152,8 @@ static int nft_flow_offload_rule(struct nft_trans *trans,if (flow) proto = flow->proto; -nft_flow_offload_common_init (&cls_flow.common, proto, &extack); +nft_flow_offload_common_init (&cls_flow.common, proto, + basechain->ops.priority, &extack); cls_flow.command = command; cls_flow.cookie = (unsigned long ) rule;if (flow)
Signature · 1 line
2.11.0
Re: [PATCH net,v5 2/2] netfilter: nf_tables: map basechain priority to hardware priority
Quoted 7 lines · Pablo Neira Ayuso
This patch adds initial support for offloading basechains using the priority range from 1 to 65535. This is restricting the netfilter priority range to 16-bit integer since this is what most drivers assume so far from tc. It should be possible to extend this range of supported priorities later on once drivers are updated to support for 32-bit integer priorities.
Quoted 6 lines
Signed-off-by Pablo Neira Ayuso <[email protected]>---
v5: fix clang warning by simplifying the mapping of hardware priorities
to basechain priority in the range of 1-65535. Zero is left behind since some drivers do not support this, no negative basechain priorities are used at this stage.
LGTM.
David Miller
maintainerFrom: Pablo Neira Ayuso <[email protected]>
Date: Fri, 16 Aug 2019 03:24:08 +0200
Quoted 6 lines
This patchset contains two updates for the
flow_offloadusers:1) Pass the major tc priority to drivers so they do not have to lshift it. This is a preparation patch for the fix coming in patch #2.
Quoted 6 lines
2) Set the hardware priority from the netfilter basechain priority, some drivers break when using the existing hardware priority number that is set to zero.
v5: fix patch 2/2 to address a clang warning and to simplify
the priority mapping.
Series applied.