[dpdk-dev] [Bug 840] [dpdk-21.11] vm2vm_virtio_user/vm2vm_virtio_user_split_virtqueue_mergeable_path: dpdk-pdump capture the pcap file content are wrong

[dpdk-dev] [Bug 840] [dpdk-21.11] vm2vm_virtio_user/vm2vm_virtio_user_split_virtqueue_mergeable_path: dpdk-pdump capture the pcap file content are wrong

[bugzilla]

https://bugs.dpdk.org/show_bug.cgi?id=840

            Bug ID: 840
           Summary: [dpdk-21.11]
                    vm2vm_virtio_user/vm2vm_virtio_user_split_virtqueue_me
                    rgeable_path: dpdk-pdump capture the pcap file content
                    are wrong
           Product: DPDK
           Version: 21.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: other
          Assignee: dev@dpdk.org
          Reporter: weix.ling@intel.com
  Target Milestone: ---

Created attachment 173
  --> https://bugs.dpdk.org/attachment.cgi?id=173&action=edit
wrong content in pcap file

Environment

DPDK version: 
 DPDK-21.11-rc1:6c390cee976e33b1e9d8562d32c9d3ebe5d9ce94
Other software versions: N/A
OS: Ubuntu 20.04.3 LTS/Linux 5.8.0-48-generic
Compiler: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
Hardware platform: Intel(R) Xeon(R) Platinum 8280M CPU @ 2.70GHz
NIC hardware: Intel Corporation Ethernet Controller XL710 for 40GbE QSFP+ (rev
02) 
NIC firmware & driver: 
driver: i40e
version: 2.17.1
firmware-version: 8.30 0x8000a4ae 1.2926.0


Test Setup
Steps to reproduce
List the steps to reproduce the issue.

1. Start vhost-user:

x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 1,2 -n 4 
--file-prefix=vhost_28751_20211027111543 --no-pci  --vdev
'net_vhost0,iface=./vhost-net0,queues=1' --vdev
'net_vhost1,iface=./vhost-net1,queues=1'  -- -i --nb-cores=1 --no-flush-rx

testpmd> set fwd io

2. Start virtio-user1:

x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 5,6 -n 4  --file-prefix=virtio1
--no-pci  --socket-mem 1024,1024
--vdev=net_virtio_user1,mac=00:01:02:03:04:05,path=./vhost-net1,queues=1,packed_vq=0,mrg_rxbuf=1,in_order=0,queue_size=256
--single-file-segments -- -i --nb-cores=1 --txd=256 --rxd=256

testpmd> set fwd rxonly
testpmd> start

3. Start pdump-user:

x86_64-native-linuxapp-gcc/app/dpdk-pdump  -l 1,2 -n 4   --file-prefix=virtio1 
 -v -- --pdump 
'device_id=net_virtio_user1,queue=*,rx-dev=/tmp/pdump-virtio-rx.pcap,mbuf-size=8000'

4. Start virtio-user0 and send 251 64B size packets and send 5 8k size packets:

x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 3,4 -n 4  --file-prefix=virtio0
--no-pci  --socket-mem 1024,1024
--vdev=net_virtio_user0,mac=00:01:02:03:04:05,path=./vhost-net0,queues=1,packed_vq=0,mrg_rxbuf=1,in_order=0,queue_size=256
--single-file-segments -- -i --nb-cores=1 --txd=256 --rxd=256

testpmd> set burst 1
testpmd> start tx_first 27
testpmd> stop
testpmd> set burst 32
testpmd> start tx_first 7
testpmd> stop
testpmd> set burst 32
testpmd> set txpkts 2000,2000,2000,2000
testpmd> start tx_first 1

5. Send start command in vhost-user testpmd:
testpmd> start

6. Send 32 2k pakckets from virtio-user0:
testpmd> stop
testpmd> set burst 32
testpmd> set txpkts 2000
testpmd> start tx_first 1

7. Send Ctrl + C command to stop the pdump and quit command to quit the
vhost-user, virtio-user1 and virtio-user0

8. Check the content in the dpdk-pdump caputer file /tmp/pdump-virtio-rx.pcap.
Show the output from the previous commands.

The content in the /tmp/pdump-virtio-rx.pcap file are wrong.
View attachment pdump-virtio-rx_bug.pcap for more details.
Expected Result
Explain what is the expected result in text or as an example output:

The content in the /tmp/pdump-virtio-rx.pcap file are wrong, it clude 251 64B
size packets, 5 8k size packets and 32 2k size packets, total 288 packets.
Regression
Is this issue a regression: (Y)

Version the regression was introduced: Specify git id if known.

commit 10f726efe26c55805cf0bf6ca1b80e97b98eb724    //bad commit id

Author: Stephen Hemminger <stephen@networkplumber.org>

commit 745b7587f9e52a4df2121d7214346853b4baf5ed   //build faild
commit 2eccf6afbea99dcabb9843c48088097796be8a33     //build faild
commit 80da61198b6be66ab16964eb0944c79c0325c40e    //build faild
commit 8dd1a4e4ff402c970c45003542c17e1e3501c540    //build faild
commit 7a944656b33fe24031f5574860eb81871403d5e3    //build faild
commit 8d23ce8f5ee9f34acd1646b01ae6d862f5fd2aa2    //good commit id

-- 
You are receiving this mail because:
You are the assignee for the bug.