From: Anupama Laxmi <anupamalaxmi4@gmail.com>
To: users@dpdk.org
Subject: Re: [dpdk-users] UDP bad checksum errors
Date: Mon, 24 Sep 2018 22:28:50 +0530 [thread overview]
Message-ID: <CA+17DaVPTKhPx9ayXQrRFJen5-q3Hz7ZvN1Jw__oe=D+FDhGKw@mail.gmail.com> (raw)
In-Reply-To: <CA+17DaUx1u=BgaNq6c2tVt1HQ0jrx+Ddyfn_P8rMc-jXdcwq0g@mail.gmail.com>
UDP checksum is set to 0 and Hardware offloading is disabled to prevent
the UDP checksum errors.
Is this the only way out?Is there Hardware virtualization limitation with
respect to UDP checksum computation?Please suggest how to resolve UDP bad
checksum errors with Hardware offloading set ?
On Mon, Sep 24, 2018 at 10:18 PM Anupama Laxmi <anupamalaxmi4@gmail.com>
wrote:
> Hi,
>
> UDP checksum cannot be computed by Hardware virtualization( Intel 82599
> SRIOV PCI passthrough, DPDK V1.7 ).UDP bad checksum errors are observed in
> the tcpdump(pcap) collected after host on the Service router when the UDP
> checksum computation is Hardware offloaded.
>
> Thanks,
>
>
>
prev parent reply other threads:[~2018-09-24 16:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 16:48 Anupama Laxmi
2018-09-24 16:58 ` Anupama Laxmi [this message]
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='CA+17DaVPTKhPx9ayXQrRFJen5-q3Hz7ZvN1Jw__oe=D+FDhGKw@mail.gmail.com' \
--to=anupamalaxmi4@gmail.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).