27911a6e62
There are difference about queue's interrupt configurations for different versions of hardware network engine, such as queue's interrupt mapping mode, coalesce configuration, etc. The following uses the configuration differences of the interrupt mapping mode as an example. 1) For some versions of hardware network engine, such as kunpeng 920, because of the hardware constraint, we need implement unmmapping relationship configurations by binding all queues to the last interrupt vector and reserving the last interrupt vector. This results in a decrease of the maximum queues when upper applications call the rte_eth_dev_configure API function to enable Rx interrupt. 2) And for another versions, such as kunpeng 930, hns3 PMD driver can map/unmmap all interrupt vectors with queues when Rx interrupt is enabled. This patch resolves configuration differences about Rx interrupts based on kunpeng 920 and kunpeng 930. Signed-off-by: Wei Hu (Xavier) <xavier.huwei@huawei.com> |
||
---|---|---|
.. | ||
hns3_cmd.c | ||
hns3_cmd.h | ||
hns3_dcb.c | ||
hns3_dcb.h | ||
hns3_ethdev_vf.c | ||
hns3_ethdev.c | ||
hns3_ethdev.h | ||
hns3_fdir.c | ||
hns3_fdir.h | ||
hns3_flow.c | ||
hns3_intr.c | ||
hns3_intr.h | ||
hns3_logs.h | ||
hns3_mbx.c | ||
hns3_mbx.h | ||
hns3_mp.c | ||
hns3_mp.h | ||
hns3_regs.c | ||
hns3_regs.h | ||
hns3_rss.c | ||
hns3_rss.h | ||
hns3_rxtx.c | ||
hns3_rxtx.h | ||
hns3_stats.c | ||
hns3_stats.h | ||
meson.build | ||
rte_pmd_hns3_version.map |