From: Thomas Monjalon <thomas@monjalon.net>
To: Nipun Gupta <nipun.gupta@amd.com>
Cc: dev@dpdk.org, Ferruh.Yigit@amd.com, david.marchand@redhat.com,
xuan.ding@intel.com, nikhil.agarwal@amd.com,
xingguang.he@intel.com, weix.ling@intel.com,
Nipun Gupta <nipun.gupta@amd.com>
Subject: Re: [PATCH] doc: add information to update dma entry limit
Date: Wed, 05 Jul 2023 14:56:29 +0200 [thread overview]
Message-ID: <38378088.10thIPus4b@thomas> (raw)
In-Reply-To: <20230705105307.5495-1-nipun.gupta@amd.com>
05/07/2023 12:53, Nipun Gupta:
> VFIO module provides configurable dma_entry_limit
> parameter to store the DMA entries. By default this
> is 64K and if we are using --no-huge, we shall need
> to increase the value of dma_entry_limit. Add
> commands in linux_gsg document to change the
> dma_entry_limit.
>
> Signed-off-by: Nipun Gupta <nipun.gupta@amd.com>
> ---
> doc/guides/linux_gsg/linux_drivers.rst | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/doc/guides/linux_gsg/linux_drivers.rst b/doc/guides/linux_gsg/linux_drivers.rst
> index 2cec1ebede..b729bb38a8 100644
> --- a/doc/guides/linux_gsg/linux_drivers.rst
> +++ b/doc/guides/linux_gsg/linux_drivers.rst
> @@ -180,6 +180,21 @@ VFIO module parameter ``dma_entry_limit`` with a default value of 64K.
> When application is out of DMA entries, these limits need to be adjusted to
> increase the allowed limit.
>
> +When ``no-huge`` parameter is used, the page size used is of smaller size of
I would add "--" to have the full option "--no-huge".
By the way, this is an "option" in the shell language :-)
> +``4K`` or ``64K`` and we shall need to increase ``dma_entry_limit``.
> +To update the ``dma_entry_limit``, ``vfio_iommu_type1`` has to be loaded with
> +additional module parameter:
> +
> +.. code-block:: console
> +
> + modprobe vfio_iommu_type1 dma_entry_limit=512000
> +
> +Alternatively, one can also change this value in an already loaded kernel module:
> +
> +.. code-block:: console
> +
> + echo 512000 > /sys/module/vfio_iommu_type1/parameters/dma_entry_limit
That looks good, thank you.
next prev parent reply other threads:[~2023-07-05 12:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 10:53 [PATCH] doc: add information to update dma entry limit Nipun Gupta
2023-07-05 12:56 ` Thomas Monjalon [this message]
2023-07-05 13:39 ` [PATCH v2] " Nipun Gupta
2023-07-20 5:05 ` 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=38378088.10thIPus4b@thomas \
--to=thomas@monjalon.net \
--cc=Ferruh.Yigit@amd.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=nikhil.agarwal@amd.com \
--cc=nipun.gupta@amd.com \
--cc=weix.ling@intel.com \
--cc=xingguang.he@intel.com \
--cc=xuan.ding@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.