Hi, Feifei
Sorry, I do not follow what this patch fixes. Do we have some issue/bug with MR
cache in practice?
Each Tx queue has its own dedicated "local" cache for MRs to convert buffer
address in mbufs being transmitted
to LKeys (HW-related entity handle) and the "global" cache for all MR
registered on the device.
AFAIK, how conversion happens in datapath:
- check the local queue cache flush request
- lookup in local cache
- if not found:
- acquire lock for global cache read access
- lookup in global cache
- release lock for global cache
How cache update on memory freeing/unregistering happens:
- acquire lock for global cache write access
- [a] remove relevant MRs from the global cache
- [b] set local caches flush request
- free global cache lock
If I understand correctly, your patch swaps [a] and [b],
and local caches flush is requested earlier. What problem does it solve?
It is not supposed there are in datapath some mbufs referencing
to the memory being freed. Application must ensure this and must not allocate
new mbufs from this memory regions being freed. Hence, the lookups for these
MRs in caches should not occur.
For other side, the cache flush has negative effect - the local cache is
getting empty and can't provide translation for other valid (not being removed)
MRs,
and the translation has to look up in the global cache, that is locked now
for rebuilding, this causes the delays in datapatch on acquiring global cache
lock.
So, I see some potential performance impact.
With best regards,
Slava
> -----Original Message-----
> From: Feifei Wang <feifei.wa...@arm.com>
> Sent: Thursday, March 18, 2021 9:19
> To: Matan Azrad <ma...@nvidia.com>; Shahaf Shuler
> <shah...@nvidia.com>; Slava Ovsiienko <viachesl...@nvidia.com>;
> Yongseok Koh <ys...@mellanox.com>
> Cc: dev@dpdk.org; n...@arm.com; Feifei Wang <feifei.wa...@arm.com>;
> sta...@dpdk.org; Ruifeng Wang <ruifeng.w...@arm.com>
> Subject: [PATCH v1 3/4] net/mlx5: fix rebuild bug for Memory Region cache
>
> 'dev_gen' is a variable to inform other cores to flush their local cache when
> global cache is rebuilt.
>
> However, if 'dev_gen' is updated after global cache is rebuilt, other cores
> may load a wrong memory region lkey value from old local cache.
>
> Timeslot main core worker core
> 1 rebuild global cache
> 2 load unchanged dev_gen
> 3 update dev_gen
> 4 look up old local cache
>
> From the example above, we can see that though global cache is rebuilt, due
> to that dev_gen is not updated, the worker core may look up old cache table
> and receive a wrong memory region lkey value.
>
> To fix this, updating 'dev_gen' should be moved before rebuilding global
> cache to inform worker cores to flush their local cache when global cache
> start rebuilding. And wmb can ensure the sequence of this process.
>
> Fixes: 974f1e7ef146 ("net/mlx5: add new memory region support")
> Cc: sta...@dpdk.org
>
> Suggested-by: Ruifeng Wang <ruifeng.w...@arm.com>
> Signed-off-by: Feifei Wang <feifei.wa...@arm.com>
> Reviewed-by: Ruifeng Wang <ruifeng.w...@arm.com>
> ---
> drivers/net/mlx5/mlx5_mr.c | 37 +++++++++++++++++--------------------
> 1 file changed, 17 insertions(+), 20 deletions(-)
>
> diff --git a/drivers/net/mlx5/mlx5_mr.c b/drivers/net/mlx5/mlx5_mr.c index
> da4e91fc2..7ce1d3e64 100644
> --- a/drivers/net/mlx5/mlx5_mr.c
> +++ b/drivers/net/mlx5/mlx5_mr.c
> @@ -103,20 +103,18 @@ mlx5_mr_mem_event_free_cb(struct
> mlx5_dev_ctx_shared *sh,
> rebuild = 1;
> }
> if (rebuild) {
> - mlx5_mr_rebuild_cache(&sh->share_cache);
> + ++sh->share_cache.dev_gen;
> + DEBUG("broadcasting local cache flush, gen=%d",
> + sh->share_cache.dev_gen);
> +
> /*
> * Flush local caches by propagating invalidation across cores.
> - * rte_smp_wmb() is enough to synchronize this event. If
> one of
> - * freed memsegs is seen by other core, that means the
> memseg
> - * has been allocated by allocator, which will come after this
> - * free call. Therefore, this store instruction (incrementing
> - * generation below) will be guaranteed to be seen by other
> core
> - * before the core sees the newly allocated memory.
> + * rte_smp_wmb() is to keep the order that dev_gen
> updated before
> + * rebuilding global cache. Therefore, other core can flush
> their
> + * local cache on time.
> */
> - ++sh->share_cache.dev_gen;
> - DEBUG("broadcasting local cache flush, gen=%d",
> - sh->share_cache.dev_gen);
> rte_smp_wmb();
> + mlx5_mr_rebuild_cache(&sh->share_cache);
> }
> rte_rwlock_write_unlock(&sh->share_cache.rwlock);
> }
> @@ -407,20 +405,19 @@ mlx5_dma_unmap(struct rte_pci_device *pdev,
> void *addr,
> mlx5_mr_free(mr, sh->share_cache.dereg_mr_cb);
> DEBUG("port %u remove MR(%p) from list", dev->data->port_id,
> (void *)mr);
> - mlx5_mr_rebuild_cache(&sh->share_cache);
> +
> + ++sh->share_cache.dev_gen;
> + DEBUG("broadcasting local cache flush, gen=%d",
> + sh->share_cache.dev_gen);
> +
> /*
> * Flush local caches by propagating invalidation across cores.
> - * rte_smp_wmb() is enough to synchronize this event. If one of
> - * freed memsegs is seen by other core, that means the memseg
> - * has been allocated by allocator, which will come after this
> - * free call. Therefore, this store instruction (incrementing
> - * generation below) will be guaranteed to be seen by other core
> - * before the core sees the newly allocated memory.
> + * rte_smp_wmb() is to keep the order that dev_gen updated
> before
> + * rebuilding global cache. Therefore, other core can flush their
> + * local cache on time.
> */
> - ++sh->share_cache.dev_gen;
> - DEBUG("broadcasting local cache flush, gen=%d",
> - sh->share_cache.dev_gen);
> rte_smp_wmb();
> + mlx5_mr_rebuild_cache(&sh->share_cache);
> rte_rwlock_read_unlock(&sh->share_cache.rwlock);
> return 0;
> }
> --
> 2.25.1
