All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 771] [dpdk-21.08]loopback csum fwd performance drop when fwd 8k large pkts
Date: Wed, 04 Aug 2021 06:57:49 +0000	[thread overview]
Message-ID: <bug-771-3@http.bugs.dpdk.org/> (raw)

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

            Bug ID: 771
           Summary: [dpdk-21.08]loopback csum fwd performance drop when
                    fwd 8k large pkts
           Product: DPDK
           Version: 21.08
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: vhost/virtio
          Assignee: dev@dpdk.org
          Reporter: weix.ling@intel.com
  Target Milestone: ---

Reproduce step:
1.Launch vhost:
./x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 32-33 -n 4 --no-pci     --vdev
'eth_vhost0,iface=vhost-net0,queues=1,client=1' -- -i --nb-cores=1
set fwd csum
start

2. Launch virtio:
x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 30,31 -n 4 
--file-prefix=testpmd0 --no-pci 
--vdev=net_virtio_user0,mac=00:11:22:33:44:10,path=./vhost-net0,queues=1,mrg_rxbuf=1,in_order=0,vectorized=1,packed_vq=1,server=1
-- -i
set fwd csum
set txpkts 2000,2000,2000,2000
start tx_first 32
show port stats all  


Performance result:
commit 8f09758941bc93f80525b2b56f85dcf1bd6bd295                   
expected performance:  2140859pps  (w/o your patch set)

commit 9af79db20f4cf75 testpmd loopback performance                
perf drop to :  727921 pps (w/ your patch set)

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

                 reply	other threads:[~2021-08-04  6:57 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-771-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.