summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorShreyansh Jain <shreyansh.jain@nxp.com>2019-04-25 15:10:19 +0530
committerThomas Monjalon <thomas@monjalon.net>2019-05-03 00:47:58 +0200
commitf0a26885b3003c89d5680a41a5e3c7e59d7c1989 (patch)
treee9218dd9b8e68e15583eeed37d7621ca9159d284 /doc
parent8bd5f07c7a1ac0c5b8d16758efc3ada3e16b0adc (diff)
downloaddpdk-draft-windows-f0a26885b3003c89d5680a41a5e3c7e59d7c1989.zip
dpdk-draft-windows-f0a26885b3003c89d5680a41a5e3c7e59d7c1989.tar.gz
dpdk-draft-windows-f0a26885b3003c89d5680a41a5e3c7e59d7c1989.tar.xz
examples/l3fwd: support separate buffer pool per port
Traditionally, only a single buffer pool per port (or, per-port-per-socket) is created in l3fwd application. If separate pools are created per-port, it might lead to gain in performance as packet alloc/dealloc requests would be isolated across ports (and their corresponding lcores). This patch adds an argument '--per-port-pool' to the l3fwd application. By default, old mode of single pool per port (split on sockets) is active. L3fwd user guide is also updated by this patch. Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com> Acked-by: Ruifeng Wang <ruifeng.wang@arm.com>
Diffstat (limited to 'doc')
-rw-r--r--doc/guides/sample_app_ug/l3_forward.rst3
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/guides/sample_app_ug/l3_forward.rst b/doc/guides/sample_app_ug/l3_forward.rst
index ddd0f9a..670918c 100644
--- a/doc/guides/sample_app_ug/l3_forward.rst
+++ b/doc/guides/sample_app_ug/l3_forward.rst
@@ -55,6 +55,7 @@ The application has a number of command line options::
[--hash-entry-num]
[--ipv6]
[--parse-ptype]
+ [--per-port-pool]
Where,
@@ -83,6 +84,8 @@ Where,
* ``--parse-ptype:`` Optional, set to use software to analyze packet type. Without this option, hardware will check the packet type.
+* ``--per-port-pool:`` Optional, set to use independent buffer pools per port. Without this option, single buffer pool is used for all ports.
+
For example, consider a dual processor socket platform with 8 physical cores, where cores 0-7 and 16-23 appear on socket 0,
while cores 8-15 and 24-31 appear on socket 1.