Re: [dpdk-dev] mlx5 FDIR rule comparison issue

Thanks Dekel for your information. I will have a try. Bests, Daniel > On Apr 4, 2019, at 7:18 PM, Dekel Peled wrote: > > Hi Daniel, > > The flow_director API will be deprecated in the near future. > It was replaced by rte_flow API, which contains much more features, and is > fully supported b

Re: [dpdk-dev] mlx5 FDIR rule comparison issue

Hi Daniel, The flow_director API will be deprecated in the near future. It was replaced by rte_flow API, which contains much more features, and is fully supported by Mellanox. It is recommended that you use rte_flow API in your application. Regards, Dekel > -Original Message- > From: b

Re: [dpdk-dev] mlx5 FDIR rule comparison issue

+Dekel Add Dekel to see if this is an issue. Thanks, Daniel > On Apr 2, 2019, at 3:23 PM, benli ye wrote: > > Hi Developers, > > I am adding two FDIR rule (one is for UDP and the other is for TCP) for mlx5 > pmd driver. The rules are listed below. >struct rte_eth_fdir_filter filt[MAX_FDI

[dpdk-dev] mlx5 FDIR rule comparison issue

Hi Developers, I am adding two FDIR rule (one is for UDP and the other is for TCP) for mlx5 pmd driver. The rules are listed below. struct rte_eth_fdir_filter filt[MAX_FDIR_PROTO] = { { .input.flow_type = RTE_ETH_FLOW_NONFRAG_IPV4_TCP, .input.flow.tcp4_flow.ip.