[dpdk-dev] [PATCH 0/3] fix the issue sctp flow cannot be matched in FVL FDIR
> > This patch set fixes the issue SCTP flow cannot be matched by FVL's flow > > director. The issue's root cause is that due to the NIC's firmware update, > > the input set of sctp flow are changed to source IP, destination IP, > > source port, destination port and Verification-Tag, which are source IP, > > destination IP and Verification-Tag previously. > > And because this fix will affect the struct rte_eth_fdir_flow, use > > RTE_NEXT_ABI to avoid ABI breaking. > > > > Jingjing Wu (3): > > ethdev: change the input set of sctp flow > > i40e: make sport and dport of sctp flow involved in match > > testpmd: add sport and dport configuration for sctp flow > > Tested-by: Marvin Liu Applied, thanks An ABI deprecation announce must be sent.
[dpdk-dev] [PATCH 0/3] fix the issue sctp flow cannot be matched in FVL FDIR
This patch set fixes the issue SCTP flow cannot be matched by FVL's flow director. The issue's root cause is that due to the NIC's firmware update, the input set of sctp flow are changed to source IP, destination IP, source port, destination port and Verification-Tag, which are source IP, destination IP and Verification-Tag previously. And because this fix will affect the struct rte_eth_fdir_flow, use RTE_NEXT_ABI to avoid ABI breaking. Jingjing Wu (3): ethdev: change the input set of sctp flow i40e: make sport and dport of sctp flow involved in match testpmd: add sport and dport configuration for sctp flow app/test-pmd/cmdline.c | 12 drivers/net/i40e/i40e_fdir.c| 18 ++ lib/librte_ether/rte_eth_ctrl.h | 8 3 files changed, 38 insertions(+) -- 1.9.3
[dpdk-dev] [PATCH 0/3] fix the issue sctp flow cannot be matched in FVL FDIR
Hi, > -Original Message- > From: Wu, Jingjing > Sent: Tuesday, July 07, 2015 3:58 PM > To: dev at dpdk.org > Cc: Wu, Jingjing; Liu, Yong; Xu, HuilongX > Subject: [PATCH 0/3] fix the issue sctp flow cannot be matched in FVL FDIR > > This patch set fixes the issue SCTP flow cannot be matched by FVL's flow > director. The issue's root cause is that due to the NIC's firmware update, > the input set of sctp flow are changed to source IP, destination IP, > source port, destination port and Verification-Tag, which are source IP, > destination IP and Verification-Tag previously. > And because this fix will affect the struct rte_eth_fdir_flow, use > RTE_NEXT_ABI to avoid ABI breaking. > > Jingjing Wu (3): > ethdev: change the input set of sctp flow > i40e: make sport and dport of sctp flow involved in match > testpmd: add sport and dport configuration for sctp flow > > app/test-pmd/cmdline.c | 12 > drivers/net/i40e/i40e_fdir.c| 18 ++ > lib/librte_ether/rte_eth_ctrl.h | 8 > 3 files changed, 38 insertions(+) > > -- > 1.9.3 Tested-by: Marvin Liu
