I Allain, Please see below
On Tue, Mar 28, 2017 at 04:16:08PM +0000, Legacy, Allain wrote: > > -----Original Message----- > > From: Nélio Laranjeiro [mailto:nelio.laranje...@6wind.com] > > Sent: Tuesday, March 28, 2017 11:36 AM > <..> > > If I understand correctly, your application is adding 500 rules like: > > > > flow create 0 ingress pattern eth src is <smac> dst is <dmac> / vlan vid is > > <vid> / end action mark id is <id> / queue index 0 / end > > > > Almost... the only difference is that the ETH pattern also checks for > type=0x8100 Ethernet type was not supported in DPDK 17.02, it was submitted later in march [1]. Did you embed the patch in your test? > > > Once the flows are setup, the application then checks that ingress > > > packets are properly marked with the intended unique integer specified > > > in the MARK action. > > > > It is sending packets to verify this? > > The traffic generator continues to send packets during the test. > Once all flow rules have been created the application expects further > ingress packets will be marked with the unique ID. > > > > When I run this test after the NIC has been reset there are no issues. > > > > What do you mean by "reset"? > > The DPDK test application is quit and restarted therefore the NIC is > re-probed, configured, started, etc. Seems like this is cleaning up > whatever problem is resident in the NIC that is causing the new flow > rules to not work properly. > > > > In mlx5 PMD rte_flow_destroy() always returns success as the destruction > > should never fail. > > Can you compile in debug mode (by setting > > CONFIG_RTE_LIBRTE_MLX5_DEBUG to "y")? Then you should have as many > > print for the creation rules than the destroyed ones. > > I can give that a try. Thanks, [1] http://dpdk.org/ml/archives/dev/2017-March/058722.html -- Nélio Laranjeiro 6WIND
