previously .rte_config was made at /var/run/.rte_config
for root users and $HOME/.rte_config for non-root users
now the file is renamed to config
 and is created at /var/run/dpdk/rte/config
for root users and /run/user/$EUID/dpdk/rte/config for non-root users
the docmentation of multi_proc_support has been updated
 to reflect this change

Signed-off-by: Muhammad Jawad Hussain <jawad.huss...@emumba.com>
---
 doc/guides/prog_guide/multi_proc_support.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/guides/prog_guide/multi_proc_support.rst 
b/doc/guides/prog_guide/multi_proc_support.rst
index 815e8bdc43..a409769b9c 100644
--- a/doc/guides/prog_guide/multi_proc_support.rst
+++ b/doc/guides/prog_guide/multi_proc_support.rst
@@ -113,8 +113,8 @@ Support for this usage scenario is provided using the 
``--file-prefix`` paramete
 
 By default, the EAL creates hugepage files on each hugetlbfs filesystem using 
the rtemap_X filename,
 where X is in the range 0 to the maximum number of hugepages -1.
-Similarly, it creates shared configuration files, memory mapped in each 
process, using the /var/run/.rte_config filename,
-when run as root (or $HOME/.rte_config when run as a non-root user;
+Similarly, it creates shared configuration files, memory mapped in each 
process, using the /var/run/dpdk/rte/config filename,
+when run as root (or /run/user/$EUID/dpdk/rte/config when run as a non-root 
user;
 if filesystem and device permissions are set up to allow this).
 The rte part of the filenames of each of the above is configurable using the 
file-prefix parameter.
 
-- 
2.32.0

Reply via email to