Difference between revisions of "VPP/HostStack/EchoClientServer"
From fd.io
Florin.coras (Talk | contribs) (→Builtin Echo Server/Client) |
Florin.coras (Talk | contribs) |
||
| Line 17: | Line 17: | ||
On vpp1: | On vpp1: | ||
| − | # test echo server fifo-size 4096 no-echo | + | # test echo server fifo-size 4096 no-echo |
On vpp2: | On vpp2: | ||
Revision as of 17:20, 9 May 2018
The host stack can be used by both internal and external, with respect to vpp, applications. For debugging and performance testing two pairs of such apps have been developed.
Builtin Echo Server/Client
These applications leverage the internal C apis to establish connections, shared memory fifos for sending and callback functions for receiving data. For simple debugging of the stack, start two debug images and:
On vpp1 (the server), from the cli do:
# test echo server uri tcp://vpp1_ip/port
and on vpp2 (the client):
# test echo client uri tcp://vpp1_ip/port
For half-duplex performance testing and using one core (main thread) the following is recommended:
On vpp1:
# test echo server fifo-size 4096 no-echo
On vpp2:
# test echo client fifo-size 4096 test-timeout 100 no-return mbytes 10000
External Echo Server/Client
These applications leverage the binary api for establishing connections and shared memory fifos for data exchanges.
