summaryrefslogtreecommitdiff
path: root/drivers/net/failsafe/failsafe_eal.c
diff options
context:
space:
mode:
authorAdrien Mazarguil <adrien.mazarguil@6wind.com>2017-10-19 18:11:09 +0200
committerFerruh Yigit <ferruh.yigit@intel.com>2017-10-26 02:33:01 +0200
commit5697a4142107ae1bc69ec13699d146b157d06652 (patch)
tree0a6ba411b6764bf29d97a4b5a128b148c9aad7d4 /drivers/net/failsafe/failsafe_eal.c
parent0ef007c9394dc062a10992bc077b21e8048eafc0 (diff)
downloaddpdk-next-eventdev-5697a4142107ae1bc69ec13699d146b157d06652.zip
dpdk-next-eventdev-5697a4142107ae1bc69ec13699d146b157d06652.tar.gz
dpdk-next-eventdev-5697a4142107ae1bc69ec13699d146b157d06652.tar.xz
net/mlx4: relax Rx queue configuration order
Various hardware limitations apply to RSS indirection tables, one of them being they must be an exact 1:1 mapping of the configured Rx queue indices. While this restriction is enforced when creating RSS flow rules, it is not the case when Rx queues themselves are created; underlying WQ numbers are assigned in turn, not according to queue index. Applications such as l3fwd-power that create Rx queues from highest to lowest index (or any other non-sequential order) thus fail to get a working RSS context. This commit postpones WQ initialization to dev_start(), once all Rx queues are configured in order to address this issue. Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.com> Acked-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
Diffstat (limited to 'drivers/net/failsafe/failsafe_eal.c')
0 files changed, 0 insertions, 0 deletions