41ec42770c
When starting VF, VF will issue reset command to PF, wait a fixed amount of time, and assume VF reset is done on PF side. However, compared with kernel PF, DPDK PF needs more time to setup. If we run DPDK PF to support DPDK VF, the original delay will not be enough. When we first start VF after PF is launched, the execution time of the statement info.msg_buf = rte_zmalloc("msg_buffer", info.buf_len, 0); in the function i40e_dev_handle_aq_msg is more than 200ms. It may cause VF start error. Since iavf can hardly trigger this issue and i40evf will be replaced by iavf in future DPDK versions, this patch provide a workaround. We extend VF reset waiting time from 200ms to 500ms so that VF can start normally when using DPDK PF and DPDK VF in most cases. Signed-off-by: Wenjun Wu <wenjun1.wu@intel.com> Acked-by: Qi Zhang <qi.z.zhang@intel.com> |
||
---|---|---|
.. | ||
base | ||
i40e_ethdev_vf.c | ||
i40e_ethdev.c | ||
i40e_ethdev.h | ||
i40e_fdir.c | ||
i40e_flow.c | ||
i40e_hash.c | ||
i40e_hash.h | ||
i40e_logs.h | ||
i40e_pf.c | ||
i40e_pf.h | ||
i40e_regs.h | ||
i40e_rxtx_vec_altivec.c | ||
i40e_rxtx_vec_avx2.c | ||
i40e_rxtx_vec_avx512.c | ||
i40e_rxtx_vec_common.h | ||
i40e_rxtx_vec_neon.c | ||
i40e_rxtx_vec_sse.c | ||
i40e_rxtx.c | ||
i40e_rxtx.h | ||
i40e_tm.c | ||
i40e_vf_representor.c | ||
meson.build | ||
rte_pmd_i40e.c | ||
rte_pmd_i40e.h | ||
version.map |