DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>, dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>,
	Anoob Joseph <anoobj@marvell.com>,
	Ankur Dwivedi <adwivedi@marvell.com>,
	Matan Azrad <matan@nvidia.com>,
	Shahaf Shuler <shahafs@nvidia.com>,
	Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
	Maxime Coquelin <maxime.coquelin@redhat.com>,
	Chenbo Xia <chenbo.xia@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: replace hugepages commands with dedicated tool
Date: Fri, 12 Feb 2021 11:55:05 +0000	[thread overview]
Message-ID: <6d6b5f40-2145-38df-6749-f3f9f581de17@intel.com> (raw)
In-Reply-To: <20210211181700.1273539-1-thomas@monjalon.net>

On 2/11/2021 6:16 PM, Thomas Monjalon wrote:
> The tool dpdk-hugepages.py, added in DPDK 20.11,
> is referenced in the guides instead of more complicate commands.
> 
> The original Linux commands are kept in linux_gsg/sys_reqs.rst
> and nics/build_and_test.rst.
> 
> Suggested-by: Stephen Hemminger <stephen@networkplumber.org>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
>   doc/guides/cryptodevs/octeontx.rst        | 4 +---
>   doc/guides/cryptodevs/octeontx2.rst       | 2 +-
>   doc/guides/howto/lm_bond_virtio_sriov.rst | 6 +++---
>   doc/guides/howto/lm_virtio_vhost_user.rst | 6 +++---
>   doc/guides/linux_gsg/sys_reqs.rst         | 2 ++
>   doc/guides/nics/build_and_test.rst        | 6 ++++++
>   doc/guides/nics/mlx4.rst                  | 2 +-
>   doc/guides/nics/mlx5.rst                  | 2 +-
>   doc/guides/nics/virtio.rst                | 2 +-
>   doc/guides/sample_app_ug/vhost.rst        | 2 +-
>   10 files changed, 20 insertions(+), 14 deletions(-)
> 
> diff --git a/doc/guides/cryptodevs/octeontx.rst b/doc/guides/cryptodevs/octeontx.rst
> index d813cb2974..a39f3f3d02 100644
> --- a/doc/guides/cryptodevs/octeontx.rst
> +++ b/doc/guides/cryptodevs/octeontx.rst
> @@ -107,9 +107,7 @@ applications.
>   
>   .. code-block:: console
>   
> -        echo 8 > /sys/kernel/mm/hugepages/hugepages-524288kB/nr_hugepages
> -        mkdir /mnt/huge
> -        mount -t hugetlbfs nodev /mnt/huge
> +   dpdk-hugepages.py --setup 4G --pagesize 512M
>   
>   Example applications can now be executed with crypto operations offloaded to
>   OCTEON TX crypto PMD.
> diff --git a/doc/guides/cryptodevs/octeontx2.rst b/doc/guides/cryptodevs/octeontx2.rst
> index a648a33cbc..d312eeb74c 100644
> --- a/doc/guides/cryptodevs/octeontx2.rst
> +++ b/doc/guides/cryptodevs/octeontx2.rst
> @@ -123,7 +123,7 @@ Another way to bind the VF would be to use the ``dpdk-devbind.py`` script:
>   
>       * Ensure that sufficient huge pages are available for your application::
>   
> -         echo 8 > /sys/kernel/mm/hugepages/hugepages-524288kB/nr_hugepages
> +         dpdk-hugepages.py --setup 4G --pagesize 512M
>   
>         Refer to :ref:`linux_gsg_hugepages` for more details.
>   
> diff --git a/doc/guides/howto/lm_bond_virtio_sriov.rst b/doc/guides/howto/lm_bond_virtio_sriov.rst
> index 16d86d122c..3e25480316 100644
> --- a/doc/guides/howto/lm_bond_virtio_sriov.rst
> +++ b/doc/guides/howto/lm_bond_virtio_sriov.rst
> @@ -581,9 +581,9 @@ Set up DPDK in the Virtual Machine
>      # virtio port is 03
>      # vf port is 04
>   
> -   cat  /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages
> -   echo 1024 > /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages
> -   cat  /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages
> +   /root/dpdk/usertools/dpdk-hugepages.py --show
> +   /root/dpdk/usertools/dpdk-hugepages.py --setup 2G
> +   /root/dpdk/usertools/dpdk-hugepages.py --show

Wouldn't be better to use 'dpdk-hugepages.py' only, or perhaps 
'./usertools/dpdk-hugepages.py' but not full path.
The dpdk path, '/root/dpdk/', assumption can be missleading.



  parent reply	other threads:[~2021-02-12 11:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-11 18:16 Thomas Monjalon
2021-02-11 19:07 ` Stephen Hemminger
2021-02-11 22:28   ` Thomas Monjalon
2021-02-12 11:55 ` Ferruh Yigit [this message]
2021-02-12 12:51   ` Thomas Monjalon

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=6d6b5f40-2145-38df-6749-f3f9f581de17@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=adwivedi@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=chenbo.xia@intel.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=shahafs@nvidia.com \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    --cc=viacheslavo@nvidia.com \
    /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).