dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1254] [dpdk-23.07] iavf performance drop 8%
Date: Tue, 20 Jun 2023 09:38:52 +0000	[thread overview]
Message-ID: <bug-1254-3@http.bugs.dpdk.org/> (raw)

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

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

            Bug ID: 1254
           Summary: [dpdk-23.07] iavf performance drop 8%
           Product: DPDK
           Version: 23.07
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: testpmd
          Assignee: dev@dpdk.org
          Reporter: yingyax.han@intel.com
  Target Milestone: ---

Steps to reproduce

1.create vfs and bind to vfio-pci
echo 1 > /sys/bus/pci/devices/0000\:31\:00.0/sriov_numvfs
echo 1 > /sys/bus/pci/devices/0000\:4b\:00.0/sriov_numvfs
ip link set ens85f0 vf 0 spoofchk off
ip link set ens85f0 vf 0 trust on
ip link set ens93f0 vf 0 spoofchk off
ip link set ens93f0 vf 0 trust on

./usertools/dpdk-devbind.py -b vfio-pci 31:01.0 4b:01.0 

2.start testpmd with io fwd
dpdk-testpmd -l 5,6,7 -n 8 --force-max-simd-bitwidth=512 -- -i --txq=2 --rxq=2
--nb-cores=2
EAL: Detected CPU lcores: 128
EAL: Detected NUMA nodes: 2
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: VFIO support initialized
EAL: Using IOMMU type 1 (Type 1)
EAL: Probe PCI driver: net_iavf (8086:1889) device: 0000:31:01.0 (socket 0)
EAL: Probe PCI driver: net_iavf (8086:1889) device: 0000:4b:01.0 (socket 0)
TELEMETRY: No legacy callbacks, legacy socket not created
Interactive-mode selected
testpmd: create a new mbuf pool <mb_pool_0>: n=163456, size=2176, socket=0
testpmd: preferred mempool ops selected: ring_mp_mc
Configuring Port 0 (socket 0)
iavf_configure_queues(): request RXDID[22] in Queue[0]
iavf_configure_queues(): request RXDID[22] in Queue[1]Port 0: link state change
eventPort 0: link state change eventPort 0: link state change eventPort 0: link
state change event
Port 0: 6A:CF:11:53:D5:96
Configuring Port 1 (socket 0)
iavf_configure_queues(): request RXDID[22] in Queue[0]
iavf_configure_queues(): request RXDID[22] in Queue[1]Port 1: link state change
eventPort 1: link state change eventPort 1: link state change eventPort 1: link
state change event
Port 1: 7E:4B:A0:11:25:5B
Checking link statuses...
Done
testpmd> start

3.Start transmit traffic from ixia.
transmit rate: 100%
frame size: 64
IP/fixed dst, ramdom src

4.Actual Result.
| Fwd_core | Frame Size | Throughput
| 2C/2T    | 64         | 80.7 Mpps 

5.Expected Result.
| Fwd_core | Frame Size | Throughput
| 2C/2T    | 64         | 87.9 Mpps 

6. DPDK Bad commit.
commit ed090599c8bdcf5788d3459a752f1bbac0cef176
Author: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date:   Mon Mar 20 12:00:21 2023 -0700     

rework atomic intrinsics fetch operations

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

[-- Attachment #2: Type: text/html, Size: 4759 bytes --]

                 reply	other threads:[~2023-06-20  9:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-1254-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@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).