net/mlx5: fix Memory Region registration
Although granularity of chunks in a mempool is a cacheline, addresses are
extended to align to page boundary for performance reason in device when
registering a MR (Memory Region). This could make some regions overlap,
then can cause Tx completion error due to incorrect LKEY search. If the
error occurs, the Tx queue will get stuck. To avoid it, end address of a
packet segment is used in LKEY search.
Fixes: b0b0938457
("net/mlx5: use buffer address for LKEY search")
Cc: stable@dpdk.org
Reported-by: Hanoch Haim <hhaim@cisco.com>
Signed-off-by: Yongseok Koh <yskoh@mellanox.com>
Acked-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
This commit is contained in:
parent
3a76da0ac8
commit
3a6f2eb8c5
@ -543,7 +543,7 @@ static __rte_always_inline uint32_t
|
||||
mlx5_tx_mb2mr(struct mlx5_txq_data *txq, struct rte_mbuf *mb)
|
||||
{
|
||||
uint16_t i = txq->mr_cache_idx;
|
||||
uintptr_t addr = rte_pktmbuf_mtod(mb, uintptr_t);
|
||||
uintptr_t addr = rte_pktmbuf_mtod_offset(mb, uintptr_t, DATA_LEN(mb));
|
||||
struct mlx5_mr *mr;
|
||||
|
||||
assert(i < RTE_DIM(txq->mp2mr));
|
||||
|
Loading…
Reference in New Issue
Block a user