test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Sun, QinX" <qinx.sun@intel.com>
To: "Sun, QinX" <qinx.sun@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH V1] tests/TestSuite_veb_switch.py modify cores list, vf-vf switch case must contain core0
Date: Tue, 20 Oct 2020 02:43:20 +0000	[thread overview]
Message-ID: <59e0d1c0212c4203a6f4026831c847be@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 327 bytes --]

Test-by: sunqin <qinx.sun@intel.com>


> -----Original Message-----
> From: sunqin <qinx.sun@intel.com>
> Sent: Tuesday, October 20, 2020 4:11 PM
> To: dts@dpdk.org
> Cc: Sun, QinX <qinx.sun@intel.com>
> Subject: [dts] [PATCH V1] tests/TestSuite_veb_switch.py modify cores list, vf-vf switch case must contain core0


[-- Attachment #2: TestVEBSwitching.log --]
[-- Type: application/octet-stream, Size: 6481 bytes --]

19/10/2020 17:01:15                            dts: 
TEST SUITE : TestVEBSwitching
19/10/2020 17:01:15                            dts: NIC :        columbiaville_25g
19/10/2020 17:01:16             dut.10.240.183.254: 
19/10/2020 17:01:16                         tester: 
19/10/2020 17:01:19               TestVEBSwitching: Test Case test_VEB_switching_inter_vfs Begin
19/10/2020 17:01:19             dut.10.240.183.254: 
19/10/2020 17:01:19                         tester: 
19/10/2020 17:01:19             dut.10.240.183.254: kill_all: called by dut and has no prefix list.
19/10/2020 17:01:30             dut.10.240.183.254: cat /sys/bus/pci/devices/0000\:03\:01.0/vendor
19/10/2020 17:01:30             dut.10.240.183.254: 0x8086
19/10/2020 17:01:30             dut.10.240.183.254: cat /sys/bus/pci/devices/0000\:03\:01.0/device
19/10/2020 17:01:31             dut.10.240.183.254: 0x1889
19/10/2020 17:01:31             dut.10.240.183.254: cat /sys/bus/pci/devices/0000\:03\:01.0/vendor
19/10/2020 17:01:31             dut.10.240.183.254: 0x8086
19/10/2020 17:01:31             dut.10.240.183.254: cat /sys/bus/pci/devices/0000\:03\:01.0/device
19/10/2020 17:01:31             dut.10.240.183.254: 0x1889
19/10/2020 17:01:31             dut.10.240.183.254: cat /sys/bus/pci/devices/0000\:03\:01.1/vendor
19/10/2020 17:01:31             dut.10.240.183.254: 0x8086
19/10/2020 17:01:31             dut.10.240.183.254: cat /sys/bus/pci/devices/0000\:03\:01.1/device
19/10/2020 17:01:31             dut.10.240.183.254: 0x1889
19/10/2020 17:01:31             dut.10.240.183.254: cat /sys/bus/pci/devices/0000\:03\:01.1/vendor
19/10/2020 17:01:31             dut.10.240.183.254: 0x8086
19/10/2020 17:01:31             dut.10.240.183.254: cat /sys/bus/pci/devices/0000\:03\:01.1/device
19/10/2020 17:01:31             dut.10.240.183.254: 0x1889
19/10/2020 17:01:31             dut.10.240.183.254: ip link set ens865f0 vf 0 mac 00:11:22:33:44:11
19/10/2020 17:01:31             dut.10.240.183.254: 
19/10/2020 17:01:31             dut.10.240.183.254: ip link set ens865f0 vf 1 mac 00:11:22:33:44:12
19/10/2020 17:01:31             dut.10.240.183.254: 
19/10/2020 17:01:34             dut.10.240.183.254: x86_64-native-linuxapp-gcc/app/dpdk-testpmd  -l 0,1,2,3 -n 4 -w 0000:03:01.0  --file-prefix=test1_20938_20201019170049   -- -i --eth-peer=0,00:11:22:33:44:12
19/10/2020 17:01:35             dut.10.240.183.254: EAL: Detected 72 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/test1_20938_20201019170049/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: No available hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL:   using IOMMU type 1 (Type 1)
EAL: Probe PCI driver: net_iavf (8086:1889) device: 0000:03:01.0 (socket 0)
EAL: No legacy callbacks, legacy socket not created
Interactive-mode selected
testpmd: create a new mbuf pool <mbuf_pool_socket_0>: n=171456, size=2176, socket=0
testpmd: preferred mempool ops selected: ring_mp_mc

Warning! port-topology=paired and odd forward ports number, the last port will pair with itself.

Configuring Port 0 (socket 0)
iavf_init_rss(): RSS is enabled by PF by default
iavf_configure_queues(): request RXDID == 22 in Queue[0]

Port 0: link state change event

Port 0: link state change event
Port 0: 00:11:22:33:44:11
Checking link statuses...
Done
19/10/2020 17:01:45             dut.10.240.183.254: set fwd txonly
19/10/2020 17:01:45             dut.10.240.183.254: 
Set txonly packet forwarding mode
19/10/2020 17:01:45             dut.10.240.183.254: set promisc all off
19/10/2020 17:01:45             dut.10.240.183.254: 
19/10/2020 17:01:56             dut.10.240.183.254: start
19/10/2020 17:01:56             dut.10.240.183.254: 
txonly packet forwarding - ports=1 - cores=1 - streams=1 - NUMA support enabled, MP allocation mode: native
Logical Core 1 (socket 0) forwards packets on 1 streams:
  RX P=0/Q=0 (socket 0) -> TX P=0/Q=0 (socket 0) peer=00:11:22:33:44:12

  txonly packet forwarding packets/burst=32
  packet len=64 - nb packet segments=1
  nb forwarding cores=1 - nb forwarding ports=1
  port 0: RX queue number: 1 Tx queue number: 1
    Rx offloads=0x0 Tx offloads=0x0
    RX queue: 0
      RX desc=512 - RX free threshold=32
      RX threshold registers: pthresh=0 hthresh=0  wthresh=0
      RX Offloads=0x0
    TX queue: 0
      TX desc=512 - TX free threshold=32
      TX threshold registers: pthresh=0 hthresh=0  wthresh=0
      TX offloads=0x0 - TX RS bit threshold=32
19/10/2020 17:01:58             dut.10.240.183.254: stop
19/10/2020 17:01:58             dut.10.240.183.254: 
Telling cores to ...
Waiting for lcores to finish...

  ---------------------- Forward statistics for port 0  ----------------------
  RX-packets: 0              RX-dropped: 0             RX-total: 0
  TX-packets: 63464416       TX-dropped: 0             TX-total: 63464416
  ----------------------------------------------------------------------------

  +++++++++++++++ Accumulated forward statistics for all ports+++++++++++++++
  RX-packets: 0              RX-dropped: 0             RX-total: 0
  TX-packets: 63464416       TX-dropped: 0             TX-total: 63464416
  ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Done.
19/10/2020 17:01:58             dut.10.240.183.254: show port stats 0
19/10/2020 17:01:58             dut.10.240.183.254: 

  ######################## NIC statistics for port 0  ########################
  RX-packets: 0          RX-missed: 0          RX-bytes:  0
  RX-errors: 0
  RX-nombuf:  0         
  TX-packets: 63464416   TX-errors: 0          TX-bytes:  4061722624

  Throughput (since last show)
  Rx-pps:            0          Rx-bps:            0
  Tx-pps:            0          Tx-bps:            0
  ############################################################################
19/10/2020 17:01:58               TestVEBSwitching: Test Case test_VEB_switching_inter_vfs Result PASSED:
19/10/2020 17:02:01             dut.10.240.183.254: quit
19/10/2020 17:02:02             dut.10.240.183.254: 

Stopping port 0...
Stopping ports...
Done

Shutting down port 0...
Closing ports...
Port 0 is closed
Done

Bye...
19/10/2020 17:02:07             dut.10.240.183.254: kill_all: called by dut and prefix list has value.
19/10/2020 17:02:08                            dts: 
TEST SUITE ENDED: TestVEBSwitching

             reply	other threads:[~2020-10-20  2:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-20  2:43 Sun, QinX [this message]
2020-10-20  8:11 sunqin
2020-10-27  8:55 ` Tu, Lijuan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=59e0d1c0212c4203a6f4026831c847be@intel.com \
    --to=qinx.sun@intel.com \
    --cc=dts@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).