t-mem 2048,2048 -- -p 0x1 \
--udp-port 4789 --nb-devices 2 --filter-type 3 --tx-checksum 1 \
--encap 1 --decap 1
Start vhost-user test environment like case vxlan_sample_encap
Send vxlan packet with Ether(dst = PF mac)/IP/UDP/vni(1000)/
Ether(dst = virtIO port0)/IP wrong chksum/ UDP wrong chksum
Verify that packet recevied by virtIO port0 and forwarded by virtIO
port1.
testpmd> show port stats all
Verify encapsulated packet received on PF device.
Verify that inner packet src and dst mac address have been conversed.
Verify that inner packet ip checksum and udp checksum were corrected.
Send vxlan packet with Ether(dst = PF mac)/IP/UDP/vni(1000)/
Ether(dst = virtIO port0)/IP wrong chksum/ TCP wrong chksum
Verify that packet recevied by virtIO port0 and forwarded by virtIO
port1.
testpmd> show port stats all
Verify encapsulated packet received on PF device.
Verify that inner packet src and dst mac address have been conversed.
Verify that inner packet ip checksum and tcp checksum were corrected.
Send vxlan packet with Ether(dst = PF mac)/IP/UDP/vni(1000)/
Ether(dst = virtIO port0)/IP wrong chksum/ SCTP wrong chksum
Verify that packet received by virtIO port0 and forwarded by virtIO
port1.
testpmd> show port stats all
Verify encapsulated packet received on PF device.
Verify that inner packet src and dst mac address have been conversed.
Verify that inner packet ip checksum and sctp checksum were corrected.
- Case: vxlan_sample_tso
Description: check vxlan sample tso work fine
Command / instruction:
Start vxlan sample with tso enable, tx checksum must enable too
For hardware limitation, tso segment size must be larger 256
tep_termination -c 0xf -n 3 --socket-mem 2048,2048 -- -p 0x1 \
--udp-port 4789 --nb-devices 2 --filter-type 3 --tx-checksum 1 \
--encap 1 --decap 1 --tso-segsz 256
Start vhost-user test environment like case vxlan_sample_encap
Send vxlan packet with Ether(dst = PF mac)/IP/UDP/vni(1000)/
Ether(dst = virtIO port0)/TCP/892 Bytes data, total length will be
1000
Verify that packet recevied by virtIO port0 and forwarded by virtIO
port1.
testpmd> show port stats all
Verify that four separated vxlan packets received on PF devices.
Make sure tcp packet payload is 256, 256, 256 and 124.
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Jijiang Liu
> Sent: Friday, May 29, 2015 3:40 PM
> To: dev at dpdk.org
> Subject: [dpdk-dev] [PATCH v2 00/10] Add a VXLAN sample
>
> This VXLAN sample simulates a VXLAN Tunnel Endpoint (VTEP) termination in
> DPDK, which is used to demonstrate the offload and filtering capabilities
> of i40 NIC for VXLAN packet.
>
> And this sample uses the basic virtio devices management function from
> vHost example, and the US-vHost interface and tunnel filtering mechanism
> to direct the traffic to/from a specific VM.
>
> In addition, this sample is also designed to show how tunneling protocols
> can be handled. For the vHost interface, we do not need to support zero
> copy/inter VM packet transfer, etc. The approaches we took would be of
> benefit to you because we put a pluggable structure in place so that the
> application could be easily extended to support a new tunneling protocol.
>
> The software framework is as follows:
>
>
>|---| |---|
>| VM-1(VNI:100) | | VM-2(VNI:200)|
>| |--| |--| | | |--| |--| |
>| |vport0| |vport1| | | |vport0| |vport1| |
>|-|--|-|--|-| |-|--|-|--|-| Guests
> \ /
> |-\---/|
> | us-vHost interface |
> | |-||--| |
> | decap| | TEP| | encap | DPDK App
> | |-||--| |
> ||||
> ||||
> ||
> |-||---|
> |tunnel filter|| IP/L4 Tx csum |
> |IP/L4 csum || TSO |
> |packet type || | NIC
> |packet recogn|| |
> |-||---|
> ||
> ||
> ||
> /---\
> VXLAN Tunnel
>
> The sample will support the followings:
> 1> Tunneling packet recognition.
>
> 2> The port of UDP tunneling is configurable
>
> 3> Directing incoming traffic to the correct queue based on