From: Abdullah Sevincer <abdullah.sevincer@intel.com>
To: dev@dpdk.org
Cc: jerinj@marvell.com, rashmi.shetty@intel.com,
pravin.pathak@intel.com, mike.ximing.chen@intel.com,
timothy.mcdaniel@intel.com, shivani.doneria@intel.com,
tirthendu.sarkar@intel.com,
Abdullah Sevincer <abdullah.sevincer@intel.com>
Subject: [PATCH v1] doc: update DLB2 documentation
Date: Mon, 26 Sep 2022 18:07:03 -0500 [thread overview]
Message-ID: <20220926230703.1388093-1-abdullah.sevincer@intel.com> (raw)
This commit updates the dlb2.rst eventdev guide to document a
new devarg. A new devarg: "default_port_allocation" added
to allow default ldb port allocation scheme.
Signed-off-by: Abdullah Sevincer <abdullah.sevincer@intel.com>
---
doc/guides/eventdevs/dlb2.rst | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
diff --git a/doc/guides/eventdevs/dlb2.rst b/doc/guides/eventdevs/dlb2.rst
index 5b21f13b68..7b01d5c070 100644
--- a/doc/guides/eventdevs/dlb2.rst
+++ b/doc/guides/eventdevs/dlb2.rst
@@ -414,3 +414,22 @@ Note that the weight may not exceed the maximum CQ depth.
--allow ea:00.0,cq_weight=all:<weight>
--allow ea:00.0,cq_weight=qidA-qidB:<weight>
--allow ea:00.0,cq_weight=qid:<weight>
+
+Default LDB Port Allocation
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+For optimal load balancing ports that map to one or more QIDs in common
+should not be in numerical sequence. The port->QID mapping is application
+dependent, but the driver interleaves port IDs as much as possible to
+reduce the likelihood of sequential ports mapping to the same QID(s).
+
+Hence, DLB uses an initial allocation of Port IDs to maximize the
+average distance between an ID and its immediate neighbors. (i.e.the
+distance from 1 to 0 and to 2, the distance from 2 to 1 and to 3, etc.).
+Initial port allocation option can be passed through devarg. If y (or Y)
+inial port allocation will be used, otherwise initial port allocation
+won't be used.
+
+ .. code-block:: console
+
+ --allow ea:00.0,default_port_allocation=<y/Y>
--
2.25.1
next reply other threads:[~2022-09-26 23:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 23:07 Abdullah Sevincer [this message]
2022-09-27 0:18 ` [PATCH v3] " Abdullah Sevincer
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=20220926230703.1388093-1-abdullah.sevincer@intel.com \
--to=abdullah.sevincer@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=mike.ximing.chen@intel.com \
--cc=pravin.pathak@intel.com \
--cc=rashmi.shetty@intel.com \
--cc=shivani.doneria@intel.com \
--cc=timothy.mcdaniel@intel.com \
--cc=tirthendu.sarkar@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 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).