[dpdk-users] vhost, vxlan, and nic TSO trouble.

Vivek Gupta vivek-g at hcl.com
Mon May 2 11:10:01 CEST 2016

How are you bursting packets from vhost interface to ixgbe nic?

Thanks & Regards
From: users [users-bounces at dpdk.org] on behalf of Matthias Gatto [matthias.gatto at outscale.com]
Sent: Monday, May 02, 2016 2:27 PM
To: users at dpdk.org
Subject: Re: [dpdk-users] vhost, vxlan, and nic TSO trouble.

On Mon, Apr 25, 2016 at 3:49 PM, Matthias Gatto
<matthias.gatto at outscale.com> wrote:
> 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.



The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents
(with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the
views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification,
distribution and / or publication of this message without the prior written consent of authorized representative of
HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
Before opening any email and/or attachments, please check them for viruses and other defects.


More information about the users mailing list