DPDK patches and discussions
 help / color / mirror / Atom feed
* [dpdk-dev]  [PATCH] doc: document memif loopback feature
@ 2020-03-09 12:12 Július Milan
  2020-03-09 14:43 ` Ferruh Yigit
  0 siblings, 1 reply; 2+ messages in thread
From: Július Milan @ 2020-03-09 12:12 UTC (permalink / raw)
  To: ferruh.yigit, dev, jgrajcia

Shows the example of how to connect 2 memif ports into loopback and test
the communication.

Signed-off-by: Július Milan <jmilan.dev@gmail.com>
---
 doc/guides/nics/memif.rst | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/doc/guides/nics/memif.rst b/doc/guides/nics/memif.rst
index 4d7f0086a..08a9fda86 100644
--- a/doc/guides/nics/memif.rst
+++ b/doc/guides/nics/memif.rst
@@ -272,3 +272,21 @@ Send ping from VPP::
     64 bytes from 192.168.1.2: icmp_seq=3 ttl=254 time=23.3927 ms
     64 bytes from 192.168.1.2: icmp_seq=4 ttl=254 time=24.2975 ms
     64 bytes from 192.168.1.2: icmp_seq=5 ttl=254 time=17.7049 ms
+
+Example: testpmd memif loopback
+-------------------------------
+In this example we will create 2 memif ports connected into loopback.
+The situation is analogous to cross connecting 2 ports of the NIC by cable.
+
+To set the loopback, just use the same socket and id with different roles::
+
+    #./testpmd --vdev=net_memif0,role=master,id=0 --vdev=net_memif1,role=slave,id=0 -- -i
+
+Then start the communication::
+
+    testpmd> start tx_first
+
+Finally we can check port stats to see the traffic::
+
+    testpmd> show port stats all
+    testpmd> show port stats all
-- 
2.17.1


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2020-03-09 14:43 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-03-09 12:12 [dpdk-dev] [PATCH] doc: document memif loopback feature Július Milan
2020-03-09 14:43 ` Ferruh Yigit

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).