patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: Dmitry Kozlyuk <dkozlyuk@nvidia.com>, stable@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>,
	Luca Boccassi <bluca@debian.org>
Subject: Re: [PATCH 21.11] doc: add more instructions for running as non-root
Date: Fri, 1 Jul 2022 16:52:52 +0100	[thread overview]
Message-ID: <48e77428-ea30-5445-6b19-fa21d441d4af@redhat.com> (raw)
In-Reply-To: <20220628202400.713098-1-dkozlyuk@nvidia.com>

On 28/06/2022 21:24, Dmitry Kozlyuk wrote:
> [ upstream commit 979bb5d493fbbce77eaaf2b4a01ee98f93f76dd9 ]
> 
> The guide to run DPDK applications as non-root in Linux
> did not provide specific instructions to configure the required access
> and did not explain why each bit is needed.
> The latter is important because running as non-root
> is one of the ways to tighten security and grant minimal permissions.
> 
> Signed-off-by: Dmitry Kozlyuk<dkozlyuk@nvidia.com>
> Acked-by: Bruce Richardson<bruce.richardson@intel.com>
> ---
> Upstream commit references things missing from 21.11:
> new dpdk-hugepages.py options and memory mapping documentation.
> The script call replaced with a direct mount command.
> Documentation reference is dropped as non-essential.
> 
>   doc/guides/linux_gsg/enable_func.rst | 85 +++++++++++++++++++---------
>   1 file changed, 58 insertions(+), 27 deletions(-)

Thanks Dmitry. Dropped original backport and applied this patch on 
branch 21.11. Kevin.


      reply	other threads:[~2022-07-01 15:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 20:24 Dmitry Kozlyuk
2022-07-01 15:52 ` Kevin Traynor [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=48e77428-ea30-5445-6b19-fa21d441d4af@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=bluca@debian.org \
    --cc=bruce.richardson@intel.com \
    --cc=dkozlyuk@nvidia.com \
    --cc=stable@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).