From: Matthias Gatto <matthias.gatto@outscale.com>
To: users@dpdk.org
Subject: [dpdk-users] vhost, vxlan, and nic TSO trouble.
Date: Mon, 25 Apr 2016 16:24:50 +0200 [thread overview]
Message-ID: <CAAsw5Begp77d0jY7BCu7jKk4XcXn5HBufPp_QRSo+Catq6sREg@mail.gmail.com> (raw)
Hi,
I'm working on a project using DPDK:
We are receiving packets from a vhost interface, then we encapsulate
them in vxlan packets, and finally we burst them into an ixgbe nic.
We set txq_flags of ixgbe nic to 0 in order to use offloading capability.
During encapsulation, we add vxlan header length to l2_len field inside mbuf.
It seems that l3_len, l4_len and tso_segsz are already set by vhost.
When we use iperf3 to test our architecture, it seems that:
- Packets with PKT_TX_TCP_CKSUM and without PKT_TX_TCP_SEG have a
correct checksum.
- Packets with PKT_TX_TCP_CKSUM and with PKT_TX_TCP_SEG are segmented
but have a bad checksum.
Do you think I've missed something ?
Thanks for your help
-- Matthias Gatto
next reply other threads:[~2016-04-25 14:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 14:24 Matthias Gatto [this message]
[not found] <CAAsw5BdmsN2OyPaTE5z33dAs49mf3MXR-NyQF=G=-zKbNq_Kog@mail.gmail.com>
2016-05-02 8:57 ` Matthias Gatto
2016-05-02 9:10 ` Vivek Gupta
2016-05-02 13:20 ` Matthias Gatto
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=CAAsw5Begp77d0jY7BCu7jKk4XcXn5HBufPp_QRSo+Catq6sREg@mail.gmail.com \
--to=matthias.gatto@outscale.com \
--cc=users@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).