DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 486] i40e driver has very bad performance when VXLAN TSO is enabled
Date: Thu, 28 May 2020 12:01:45 +0000
Message-ID: <bug-486-3@http.bugs.dpdk.org/> (raw)

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

            Bug ID: 486
           Summary: i40e driver has very bad performance when VXLAN TSO is
                    enabled
           Product: DPDK
           Version: 19.11
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: critical
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: yangyi01@inspur.com
  Target Milestone: ---

Current OVS DPDK (DPDK 19.11.x) has supported TSO on vlan, but TSO isn't
enabled on vxlan.

DPDK and pmd drivers have been ready for VXLAN TSO support, I'm trying to
enable it, the first patch [1] has been posted into ovs community, it can work
in term of functionality, but performance is very bad, it is about 40Mbps on
two network namespaces on my two servers, I used OVS DPDK in one server, the
other server used OVS kernel, performance can reach about 110Mbps when I
disabled GRO on physical interface and vxlan interface (sudo ethtool -K XXX gro
off), it is about 2Gbps when I disabled tso and keep tx checksum offload on
(sudo ip netns exec ns02 ethtool -K veth2 tso off).

I checked my code many times, I can't find out root cause, I doubt it is i40e
driver issue (I'm very sure my X710 NIC can work well in OVS kernel and vxlan
tso is enabled)


[1]
https://patchwork.ozlabs.org/project/openvswitch/patch/20200525090337.110640-1-yang_y_yi@163.com/

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

             reply	other threads:[~2020-05-28 12:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-28 12:01 bugzilla [this message]
2020-07-30  3:45 ` bugzilla

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-486-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

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ http://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git