net/mlx4: add new memory region support
This is the new design of Memory Region (MR) for mlx PMD, in order to:
- Accommodate the new memory hotplug model.
- Support non-contiguous Mempool.
There are multiple layers for MR search.
L0 is to look up the last-hit entry which is pointed by mr_ctrl->mru (Most
Recently Used). If L0 misses, L1 is to look up the address in a fixed-sized
array by linear search. L0/L1 is in an inline function -
mlx4_mr_lookup_cache().
If L1 misses, the bottom-half function is called to look up the address
from the bigger local cache of the queue. This is L2 - mlx4_mr_addr2mr_bh()
and it is not an inline function. Data structure for L2 is the Binary Tree.
If L2 misses, the search falls into the slowest path which takes locks in
order to access global device cache (priv->mr.cache) which is also a B-tree
and caches the original MR list (priv->mr.mr_list) of the device. Unless
the global cache is overflowed, it is all-inclusive of the MR list. This is
L3 - mlx4_mr_lookup_dev(). The size of the L3 cache table is limited and
can't be expanded on the fly due to deadlock. Refer to the comments in the
code for the details - mr_lookup_dev(). If L3 is overflowed, the list will
have to be searched directly bypassing the cache although it is slower.
If L3 misses, a new MR for the address should be created -
mlx4_mr_create(). When it creates a new MR, it tries to register adjacent
memsegs as much as possible which are virtually contiguous around the
address. This must take two locks - memory_hotplug_lock and
priv->mr.rwlock. Due to memory_hotplug_lock, there can't be any
allocation/free of memory inside.
In the free callback of the memory hotplug event, freed space is searched
from the MR list and corresponding bits are cleared from the bitmap of MRs.
This can fragment a MR and the MR will have multiple search entries in the
caches. Once there's a change by the event, the global cache must be
rebuilt and all the per-queue caches will be flushed as well. If memory is
frequently freed in run-time, that may cause jitter on dataplane processing
in the worst case by incurring MR cache flush and rebuild. But, it would be
the least probable scenario.
To guarantee the most optimal performance, it is highly recommended to use
an EAL option - '--socket-mem'. Then, the reserved memory will be pinned
and won't be freed dynamically. And it is also recommended to configure
per-lcore cache of Mempool. Even though there're many MRs for a device or
MRs are highly fragmented, the cache of Mempool will be much helpful to
reduce misses on per-queue caches anyway.
'--legacy-mem' is also supported.
Signed-off-by: Yongseok Koh <yskoh@mellanox.com>
2018-05-09 11:09:06 +00:00
|
|
|
/* SPDX-License-Identifier: BSD-3-Clause
|
|
|
|
* Copyright 2018 6WIND S.A.
|
|
|
|
* Copyright 2018 Mellanox Technologies, Ltd
|
|
|
|
*/
|
|
|
|
|
|
|
|
#ifndef RTE_PMD_MLX4_MR_H_
|
|
|
|
#define RTE_PMD_MLX4_MR_H_
|
|
|
|
|
|
|
|
#include <stddef.h>
|
|
|
|
#include <stdint.h>
|
|
|
|
#include <sys/queue.h>
|
|
|
|
|
|
|
|
/* Verbs headers do not support -pedantic. */
|
|
|
|
#ifdef PEDANTIC
|
|
|
|
#pragma GCC diagnostic ignored "-Wpedantic"
|
|
|
|
#endif
|
|
|
|
#include <infiniband/verbs.h>
|
|
|
|
#ifdef PEDANTIC
|
|
|
|
#pragma GCC diagnostic error "-Wpedantic"
|
|
|
|
#endif
|
|
|
|
|
|
|
|
#include <rte_ethdev.h>
|
|
|
|
#include <rte_rwlock.h>
|
|
|
|
#include <rte_bitmap.h>
|
|
|
|
|
|
|
|
/* Size of per-queue MR cache array for linear search. */
|
|
|
|
#define MLX4_MR_CACHE_N 8
|
|
|
|
|
|
|
|
/* Size of MR cache table for binary search. */
|
|
|
|
#define MLX4_MR_BTREE_CACHE_N 256
|
|
|
|
|
|
|
|
/* Memory Region object. */
|
|
|
|
struct mlx4_mr {
|
|
|
|
LIST_ENTRY(mlx4_mr) mr; /**< Pointer to the prev/next entry. */
|
|
|
|
struct ibv_mr *ibv_mr; /* Verbs Memory Region. */
|
|
|
|
const struct rte_memseg_list *msl;
|
|
|
|
int ms_base_idx; /* Start index of msl->memseg_arr[]. */
|
|
|
|
int ms_n; /* Number of memsegs in use. */
|
|
|
|
uint32_t ms_bmp_n; /* Number of bits in memsegs bit-mask. */
|
|
|
|
struct rte_bitmap *ms_bmp; /* Bit-mask of memsegs belonged to MR. */
|
|
|
|
};
|
|
|
|
|
|
|
|
/* Cache entry for Memory Region. */
|
|
|
|
struct mlx4_mr_cache {
|
|
|
|
uintptr_t start; /* Start address of MR. */
|
|
|
|
uintptr_t end; /* End address of MR. */
|
|
|
|
uint32_t lkey; /* rte_cpu_to_be_32(ibv_mr->lkey). */
|
|
|
|
} __rte_packed;
|
|
|
|
|
|
|
|
/* MR Cache table for Binary search. */
|
|
|
|
struct mlx4_mr_btree {
|
|
|
|
uint16_t len; /* Number of entries. */
|
|
|
|
uint16_t size; /* Total number of entries. */
|
|
|
|
int overflow; /* Mark failure of table expansion. */
|
|
|
|
struct mlx4_mr_cache (*table)[];
|
|
|
|
} __rte_packed;
|
|
|
|
|
|
|
|
/* Per-queue MR control descriptor. */
|
|
|
|
struct mlx4_mr_ctrl {
|
|
|
|
uint32_t *dev_gen_ptr; /* Generation number of device to poll. */
|
|
|
|
uint32_t cur_gen; /* Generation number saved to flush caches. */
|
|
|
|
uint16_t mru; /* Index of last hit entry in top-half cache. */
|
|
|
|
uint16_t head; /* Index of the oldest entry in top-half cache. */
|
|
|
|
struct mlx4_mr_cache cache[MLX4_MR_CACHE_N]; /* Cache for top-half. */
|
|
|
|
struct mlx4_mr_btree cache_bh; /* Cache for bottom-half. */
|
|
|
|
} __rte_packed;
|
|
|
|
|
|
|
|
extern struct mlx4_dev_list mlx4_mem_event_cb_list;
|
|
|
|
extern rte_rwlock_t mlx4_mem_event_rwlock;
|
|
|
|
|
|
|
|
/* First entry must be NULL for comparison. */
|
|
|
|
#define mlx4_mr_btree_len(bt) ((bt)->len - 1)
|
|
|
|
|
|
|
|
int mlx4_mr_btree_init(struct mlx4_mr_btree *bt, int n, int socket);
|
|
|
|
void mlx4_mr_btree_free(struct mlx4_mr_btree *bt);
|
|
|
|
void mlx4_mr_btree_dump(struct mlx4_mr_btree *bt);
|
2019-04-01 21:17:57 +00:00
|
|
|
uint32_t mlx4_mr_create_primary(struct rte_eth_dev *dev,
|
|
|
|
struct mlx4_mr_cache *entry, uintptr_t addr);
|
net/mlx4: add new memory region support
This is the new design of Memory Region (MR) for mlx PMD, in order to:
- Accommodate the new memory hotplug model.
- Support non-contiguous Mempool.
There are multiple layers for MR search.
L0 is to look up the last-hit entry which is pointed by mr_ctrl->mru (Most
Recently Used). If L0 misses, L1 is to look up the address in a fixed-sized
array by linear search. L0/L1 is in an inline function -
mlx4_mr_lookup_cache().
If L1 misses, the bottom-half function is called to look up the address
from the bigger local cache of the queue. This is L2 - mlx4_mr_addr2mr_bh()
and it is not an inline function. Data structure for L2 is the Binary Tree.
If L2 misses, the search falls into the slowest path which takes locks in
order to access global device cache (priv->mr.cache) which is also a B-tree
and caches the original MR list (priv->mr.mr_list) of the device. Unless
the global cache is overflowed, it is all-inclusive of the MR list. This is
L3 - mlx4_mr_lookup_dev(). The size of the L3 cache table is limited and
can't be expanded on the fly due to deadlock. Refer to the comments in the
code for the details - mr_lookup_dev(). If L3 is overflowed, the list will
have to be searched directly bypassing the cache although it is slower.
If L3 misses, a new MR for the address should be created -
mlx4_mr_create(). When it creates a new MR, it tries to register adjacent
memsegs as much as possible which are virtually contiguous around the
address. This must take two locks - memory_hotplug_lock and
priv->mr.rwlock. Due to memory_hotplug_lock, there can't be any
allocation/free of memory inside.
In the free callback of the memory hotplug event, freed space is searched
from the MR list and corresponding bits are cleared from the bitmap of MRs.
This can fragment a MR and the MR will have multiple search entries in the
caches. Once there's a change by the event, the global cache must be
rebuilt and all the per-queue caches will be flushed as well. If memory is
frequently freed in run-time, that may cause jitter on dataplane processing
in the worst case by incurring MR cache flush and rebuild. But, it would be
the least probable scenario.
To guarantee the most optimal performance, it is highly recommended to use
an EAL option - '--socket-mem'. Then, the reserved memory will be pinned
and won't be freed dynamically. And it is also recommended to configure
per-lcore cache of Mempool. Even though there're many MRs for a device or
MRs are highly fragmented, the cache of Mempool will be much helpful to
reduce misses on per-queue caches anyway.
'--legacy-mem' is also supported.
Signed-off-by: Yongseok Koh <yskoh@mellanox.com>
2018-05-09 11:09:06 +00:00
|
|
|
void mlx4_mr_mem_event_cb(enum rte_mem_event event_type, const void *addr,
|
|
|
|
size_t len, void *arg);
|
|
|
|
int mlx4_mr_update_mp(struct rte_eth_dev *dev, struct mlx4_mr_ctrl *mr_ctrl,
|
|
|
|
struct rte_mempool *mp);
|
|
|
|
void mlx4_mr_dump_dev(struct rte_eth_dev *dev);
|
|
|
|
void mlx4_mr_release(struct rte_eth_dev *dev);
|
|
|
|
|
|
|
|
/**
|
|
|
|
* Look up LKey from given lookup table by linear search. Firstly look up the
|
|
|
|
* last-hit entry. If miss, the entire array is searched. If found, update the
|
|
|
|
* last-hit index and return LKey.
|
|
|
|
*
|
|
|
|
* @param lkp_tbl
|
|
|
|
* Pointer to lookup table.
|
|
|
|
* @param[in,out] cached_idx
|
|
|
|
* Pointer to last-hit index.
|
|
|
|
* @param n
|
|
|
|
* Size of lookup table.
|
|
|
|
* @param addr
|
|
|
|
* Search key.
|
|
|
|
*
|
|
|
|
* @return
|
|
|
|
* Searched LKey on success, UINT32_MAX on no match.
|
|
|
|
*/
|
|
|
|
static __rte_always_inline uint32_t
|
|
|
|
mlx4_mr_lookup_cache(struct mlx4_mr_cache *lkp_tbl, uint16_t *cached_idx,
|
|
|
|
uint16_t n, uintptr_t addr)
|
|
|
|
{
|
|
|
|
uint16_t idx;
|
|
|
|
|
|
|
|
if (likely(addr >= lkp_tbl[*cached_idx].start &&
|
|
|
|
addr < lkp_tbl[*cached_idx].end))
|
|
|
|
return lkp_tbl[*cached_idx].lkey;
|
|
|
|
for (idx = 0; idx < n && lkp_tbl[idx].start != 0; ++idx) {
|
|
|
|
if (addr >= lkp_tbl[idx].start &&
|
|
|
|
addr < lkp_tbl[idx].end) {
|
|
|
|
/* Found. */
|
|
|
|
*cached_idx = idx;
|
|
|
|
return lkp_tbl[idx].lkey;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
return UINT32_MAX;
|
|
|
|
}
|
|
|
|
|
|
|
|
#endif /* RTE_PMD_MLX4_MR_H_ */
|