From: Muhammad Jawad Hussain <jawad.hussain@emumba.com>
To: dev@dpdk.org
Subject: Re: [PATCH] multi_proc_support.rst: updated file location for config file in documentation
Date: Thu, 11 Aug 2022 18:02:50 +0500 [thread overview]
Message-ID: <CACKbeL9+9Ro=DbqiX9Yoqz8deijoJTYwCAF4oHPJ23kzg7-C6w@mail.gmail.com> (raw)
In-Reply-To: <20220317061945.14845-1-jawad.hussain@emumba.com>
[-- Attachment #1: Type: text/plain, Size: 2028 bytes --]
Hi,
I've submitted a patch on 17th March, 2022. One of the tests is failing
and it is not related to the patch.
Following test is failing:
- ci/iol-broadcom-Functional
Can you please rerun the tests so that the patch can be submitted.
Regards,
-Jawad
On Thu, Mar 17, 2022 at 11:19 AM Muhammad Jawad Hussain <
jawad.hussain@emumba.com> wrote:
> 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.hussain@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
>
>
[-- Attachment #2: Type: text/html, Size: 2900 bytes --]
prev parent reply other threads:[~2022-08-11 13:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 6:19 Muhammad Jawad Hussain
2022-08-11 13:02 ` Muhammad Jawad Hussain [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACKbeL9+9Ro=DbqiX9Yoqz8deijoJTYwCAF4oHPJ23kzg7-C6w@mail.gmail.com' \
--to=jawad.hussain@emumba.com \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).