From: yang_y_yi <yang_y_yi@163.com>
To: dev@dpdk.org
Cc: beilei.xing@intel.com, "yangyi01@inspur.com" <yangyi01@inspur.com>
Subject: [dpdk-dev] i40e VXLAN TSO issue
Date: Tue, 26 May 2020 09:36:05 +0800 (CST) [thread overview]
Message-ID: <1776ee20.1196.1724e9f5925.Coremail.yang_y_yi@163.com> (raw)
Hi, folk
I'm trying to enable VXLAN TSO support in OVS DPDK, [1]
is RFC patch, I tested it, it can work in term of functionality, but the
performance is very bad, I don't know why, anybody can help on this? I tested it on X710, and tried dpdk
19.11 and dpdk 19.11.2, the same performance issue is
there.
I have the below questions:
#1. For large TSO packet, it is about 64K, but ret_mbuf
size is MTU of DPDK port, multi-segmented mbuf is necessary, but I checked
GSO code, it seems the attached mbuf includes packet header, anybody can help
confirm external mbuf is ok for Tx on physical dpdk port? It doesn't work per my check.
#2. Can anybody help review code [1] and find out the root cause?
Thank you in advance.
[1] https://patchwork.ozlabs.org/project/openvswitch/patch/20200525090337.110640-1-yang_y_yi@163.com/
reply other threads:[~2020-05-26 1:36 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=1776ee20.1196.1724e9f5925.Coremail.yang_y_yi@163.com \
--to=yang_y_yi@163.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=yangyi01@inspur.com \
/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).