From ebf9c7b1db2fbc09f87eed4cf8486239786fcad1 Mon Sep 17 00:00:00 2001 From: Anatoly Burakov Date: Thu, 21 Nov 2019 12:39:23 +0000 Subject: [PATCH] doc: fix a typo in EAL guide The correct name for virt2memseg API is `rte_mem_virt2memseg`, not `rte_virt2memseg`. Fixes: 950e8fb4e194 ("mem: allow registering external memory areas") Cc: stable@dpdk.org Signed-off-by: Anatoly Burakov --- doc/guides/prog_guide/env_abstraction_layer.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/guides/prog_guide/env_abstraction_layer.rst b/doc/guides/prog_guide/env_abstraction_layer.rst index 6e7c2080a4..48a2fec066 100644 --- a/doc/guides/prog_guide/env_abstraction_layer.rst +++ b/doc/guides/prog_guide/env_abstraction_layer.rst @@ -297,7 +297,7 @@ set of API's under the ``rte_extmem_*`` namespace. These API's are (as their name implies) intended to allow registering or unregistering externally allocated memory to/from DPDK's internal page table, to -allow API's like ``rte_virt2memseg`` etc. to work with externally allocated +allow API's like ``rte_mem_virt2memseg`` etc. to work with externally allocated memory. Memory added this way will not be available for any regular DPDK allocators; DPDK will leave this memory for the user application to manage. -- 2.20.1