From: "Min Hu (Connor)" <humin29@huawei.com>
To: <dev@dpdk.org>
Cc: <ferruh.yigit@intel.com>
Subject: [dpdk-dev] [PATCH v2] doc: add config file option for hns3 PMD
Date: Thu, 29 Apr 2021 14:12:07 +0800 [thread overview]
Message-ID: <1619676727-18884-1-git-send-email-humin29@huawei.com> (raw)
In-Reply-To: <1619660285-31522-1-git-send-email-humin29@huawei.com>
This patch adds description of max TQP number per PF for config file
option.
Signed-off-by: Min Hu (Connor) <humin29@huawei.com>
---
v2:
* deleted unexpected unindent.
---
doc/guides/nics/hns3.rst | 17 +++++++++++++++--
1 file changed, 15 insertions(+), 2 deletions(-)
diff --git a/doc/guides/nics/hns3.rst b/doc/guides/nics/hns3.rst
index d51d9b1..4439df5 100644
--- a/doc/guides/nics/hns3.rst
+++ b/doc/guides/nics/hns3.rst
@@ -44,11 +44,24 @@ Prerequisites
- Get the information about Kunpeng920 chip using
`<https://www.hisilicon.com/en/products/Kunpeng>`_.
-- Follow the DPDK :ref:`Getting Started Guide for Linux <linux_gsg>` to setup the basic DPDK environment.
+- Follow the DPDK :ref:`Getting Started Guide for Linux <linux_gsg>` to
+ setup the basic DPDK environment.
+Pre-Installation Configuration
+------------------------------
+
+Config File Options
+~~~~~~~~~~~~~~~~~~~
+
+The following options can be modified in the ``config/rte_config.h`` file.
+
+- ``RTE_LIBRTE_HNS3_MAX_TQP_NUM_PER_PF`` (default ``256``)
+
+ Number of MAX queues reserved for PF.
+
Runtime Config Options
-----------------------
+~~~~~~~~~~~~~~~~~~~~~~
- ``rx_func_hint`` (default ``none``)
--
2.7.4
next prev parent reply other threads:[~2021-04-29 6:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 1:38 [dpdk-dev] [PATCH] doc: add config file option for hns3 PMD Min Hu (Connor)
2021-04-29 6:12 ` Min Hu (Connor) [this message]
2021-05-04 12:57 ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
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=1619676727-18884-1-git-send-email-humin29@huawei.com \
--to=humin29@huawei.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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.