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

> fully supported by Mellanox. > > It is recommended that you use rte_flow API in your application. > > Regards, > Dekel > >> -Original Message- >> From: benli ye >> Sent: Wednesday, April 3, 2019 11:30 AM >> To: Dekel Peled >

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

[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.

[dpdk-dev] Ask help for mlx5 pmd driver

dpdk app and mlx5 pdm driver is working, the host is unreachable. Do I need to use rte_kni to create another two interface maybe called eth2 and eth3 to connect kernel stack? Any suggestions? Thanks very much! Bests, Daniel Benli Ye