|author||Yongseok Koh <email@example.com>||2019-04-01 14:17:57 -0700|
|committer||Ferruh Yigit <firstname.lastname@example.org>||2019-04-05 17:45:22 +0200|
net/mlx4: enable secondary process to register DMA memory
The Memory Region (MR) for DMA memory can't be created from secondary process due to lib/driver limitation. Whenever it is needed, secondary process can make a request to primary process through the EAL IPC channel (rte_mp_msg) which is established on initialization. Once a MR is created by primary process, it is immediately visible to secondary process because the MR list is global per a device. Thus, secondary process can look up the list after the request is successfully returned. Signed-off-by: Yongseok Koh <email@example.com> Acked-by: Shahaf Shuler <firstname.lastname@example.org>
Diffstat (limited to 'doc')
1 files changed, 0 insertions, 1 deletions
diff --git a/doc/guides/nics/mlx4.rst b/doc/guides/nics/mlx4.rst
index c8a02be..aaf1907 100644
@@ -159,7 +159,6 @@ Limitations
- For secondary process:
- Forked secondary process not supported.
- - All mempools must be initialized before rte_eth_dev_start().
- External memory unregistered in EAL memseg list cannot be used for DMA
unless such memory has been registered by ``mlx4_mr_update_ext_mp()`` in
primary process and remapped to the same virtual address in secondary