Re: [dpdk-dev] [PATCH] net/iavf: fix vector id assignment

2021-01-11 Thread Yu, DapengX
Hi Jingjing, I double checked that the max_vectors assignment statement is already ahead of RTE_MIN. And this patch do the same thing as http://patchwork.dpdk.org/patch/86118/. Since patch 86118 is ahead of this one, I guess merging 86118 is preferred. -Original Message- From: Wu, Jing

Re: [dpdk-dev] [PATCH] net/iavf: fix vector id assignment

2021-01-11 Thread Yu, DapengX
Hi Ting, The following test case is for i40e. if you want to test the case on ice, just ignore step 1. Step1: switch i40evf to iavf # sed -i '/{ RTE_PCI_DEVICE(IAVF_INTEL_VENDOR_ID, IAVF_DEV_ID_ADAPTIVE_VF) },/a { RTE_PCI_DEVICE(IAVF_INTEL_VENDOR_ID, IAVF_DEV_ID_VF) },' drivers/net/ia

Re: [dpdk-dev] [PATCH] net/iavf: fix vector id assignment

2021-01-11 Thread Wu, Jingjing
> -Original Message- > From: Xu, Ting > Sent: Tuesday, January 12, 2021 2:27 PM > To: Yu, DapengX ; Zhang, Qi Z > ; Wu, Jingjing ; Xing, Beilei > > Cc: dev@dpdk.org; Yu, DapengX ; sta...@dpdk.org > Subject: RE: [PATCH] net/iavf: fix vector id assignment > > > -Original Message

Re: [dpdk-dev] [PATCH] net/iavf: fix vector id assignment

2021-01-11 Thread Xu, Ting
> -Original Message- > From: dapengx...@intel.com > Sent: Friday, January 8, 2021 6:21 PM > To: Zhang, Qi Z ; Wu, Jingjing ; > Xing, Beilei ; Xu, Ting > Cc: dev@dpdk.org; Yu, DapengX ; sta...@dpdk.org > Subject: [PATCH] net/iavf: fix vector id assignment > > From: YU DAPENG > > The num

Re: [dpdk-dev] [PATCH] net/iavf: fix vector id assignment

2021-01-11 Thread Xie, WeiX
gt; > Cc: dev@dpdk.org; Yu, DapengX ; sta...@dpdk.org > Subject: [dpdk-dev] [PATCH] net/iavf: fix vector id assignment > > From: YU DAPENG > > The number of MSI-X interrupts on Rx shall be the minimal value of the > number of available MSI-X interrupts per VF - 1 (the 1 is

[dpdk-dev] [PATCH] net/iavf: fix vector id assignment

2021-01-08 Thread dapengx . yu
From: YU DAPENG The number of MSI-X interrupts on Rx shall be the minimal value of the number of available MSI-X interrupts per VF - 1 (the 1 is for miscellaneous interrupt) and the number of configured Rx queues. The current code break the rule because the number of available MSI-X interrupts is

Re: [dpdk-dev] [PATCH] net/iavf: fix vector id assignment

2021-01-03 Thread Yu, DapengX
net/iavf: fix vector id assignment > -Original Message- > From: dev On Behalf Of dapengx...@intel.com > Sent: Wednesday, December 30, 2020 2:54 PM > To: Wu, Jingjing ; Xing, Beilei > > Cc: dev@dpdk.org; Yu, DapengX ; sta...@dpdk.org > Subject: [dpdk-dev] [

Re: [dpdk-dev] [PATCH] net/iavf: fix vector id assignment

2021-01-03 Thread Zhang, Qi Z
> -Original Message- > From: dev On Behalf Of dapengx...@intel.com > Sent: Wednesday, December 30, 2020 2:54 PM > To: Wu, Jingjing ; Xing, Beilei > Cc: dev@dpdk.org; Yu, DapengX ; sta...@dpdk.org > Subject: [dpdk-dev] [PATCH] net/iavf: fix vector id assignment &g

Re: [dpdk-dev] [PATCH] net/iavf: fix vector id assignment

2020-12-29 Thread Xie, WeiX
k.org; Yu, DapengX ; sta...@dpdk.org > Subject: [dpdk-dev] [PATCH] net/iavf: fix vector id assignment > > From: YU DAPENG > > When the interrupt handle instance allows none packet I/O interrupts, the > max value of vector_id is set to be less than the number of msix interrupts, > but no

[dpdk-dev] [PATCH] net/iavf: fix vector id assignment

2020-12-29 Thread dapengx . yu
From: YU DAPENG When the interrupt handle instance allows none packet I/O interrupts, the max value of vector_id is set to be less than the number of msix interrupts, but not equal to it. Which may cause same vector_id is sent to PF with opcode VIRTCHNL_OP_CONFIG_IRQ_MAP to setup the cause of int