net/mlx5: Use multi threaded workqueue for page fault handling
Page fault events are processed in a workqueue context. Since each QP
can have up to two concurrent unrelated page-faults, one for requester
and one for responder, page-fault handling can be done in parallel.
Achieve this by changing the workqueue to be multi-threaded.
The number of threads is the same as the number of command interface
channels to avoid command interface bottlenecks.
In addition to multi-threads, change the workqueue flags to give it high
priority.
Stress benchmark shows that before this change 85% of page faults were
waiting in queue 8 seconds or more while after the change 98% of page
faults were waiting in queue 64 milliseconds or less. The number of threads
was chosen as the number of channels to the command interface.
Fixes: d9aaed8387
("{net,IB}/mlx5: Refactor page fault handling")
Signed-off-by: Moni Shoua <monis@mellanox.com>
Signed-off-by: Leon Romanovsky <leonro@mellanox.com>
This commit is contained in:
parent
ef90c5e975
commit
90290db766
|
@ -356,8 +356,9 @@ static int init_pf_ctx(struct mlx5_eq_pagefault *pf_ctx, const char *name)
|
|||
spin_lock_init(&pf_ctx->lock);
|
||||
INIT_WORK(&pf_ctx->work, eq_pf_action);
|
||||
|
||||
pf_ctx->wq = alloc_ordered_workqueue(name,
|
||||
WQ_MEM_RECLAIM);
|
||||
pf_ctx->wq = alloc_workqueue(name,
|
||||
WQ_HIGHPRI | WQ_UNBOUND | WQ_MEM_RECLAIM,
|
||||
MLX5_NUM_CMD_EQE);
|
||||
if (!pf_ctx->wq)
|
||||
return -ENOMEM;
|
||||
|
||||
|
|
Loading…
Reference in a new issue