On 10/27/2020 3:42 PM, Slava Ovsiienko wrote:
Hi, Bing
Release notes / mlx5 features documentation update?
Beside this:
Acked-by: Viacheslav Ovsiienko <viachesl...@nvidia.com>
-----Original Message-----
From: Bing Zhao <bi...@nvidia.com>
Sent: Tuesday, October 27, 2020 16:47
To: Slava Ovsiienko <viachesl...@nvidia.com>; Matan Azrad
<ma...@nvidia.com>; Ori Kam <or...@nvidia.com>
Cc: dev@dpdk.org; Raslan Darawsheh <rasl...@nvidia.com>
Subject: [PATCH v2 2/2] net/mlx5: add flow sync API
When creating a flow, the rule itself might not take effort immediately once
the function call returns with success. It would take some time to let the
steering synchronize with the hardware.
If the application wants the packet to be sent to hit the flow after it is
created,
this flow sync API can be used to clear the steering HW cache to enforce next
packet hits the latest rules.
For TX, usually the NIC TX domain and/or the FDB domain should be
synchronized depends in which domain the flow is created.
The application could also try to synchronize the NIC RX and/or the FDB
domain for the ingress packets.
Signed-off-by: Bing Zhao <bi...@nvidia.com>
Acked-by: Ori Kam <or...@nvidia.com>
<...>
@@ -8169,3 +8179,17 @@ int mlx5_alloc_tunnel_hub(struct
mlx5_dev_ctx_shared *sh)
mlx5_free(thub);
return err;
}
+
+int rte_pmd_mlx5_sync_flow(uint16_t port_id, uint32_t domains) {
+ struct rte_eth_dev *dev = &rte_eth_devices[port_id];
+ const struct mlx5_flow_driver_ops *fops;
+ int ret;
+ struct rte_flow_attr attr = { .transfer = 0 };
+
+ fops = flow_get_drv_ops(flow_get_drv_type(dev, &attr));
+ ret = fops->sync_domain(dev, domains,
MLX5DV_DR_DOMAIN_SYNC_FLAGS_HW);
+ if (ret > 0)
+ ret = -ret;
+ return ret;
+}
This is causing build error in the travis [1], I guess this is related to the
rdma-core version, is the 'MLX5DV_DR_DOMAIN_SYNC_FLAGS_HW' check required in the
header like other usages?
Also 'MLX5DV_' macros seems used in 'mlx5_flow_dv.c', is it expected to use it
in this file? (just high-level observation, no idea on details.)
[1] https://travis-ci.org/github/ferruhy/dpdk/jobs/740008969
btw, I just recognized that the patch acked with exception, is the documentation
requested above (with ack) provided?
