From: Andriy Berestovskyy <aber@semihalf.com>
To: Angela Czubak <ACzubak@pl.ibm.com>
Cc: dev@dpdk.org
Subject: Re: Non-working TX IP checksum offload
Date: Fri, 17 Jul 2015 16:37:45 +0200 [thread overview]
Message-ID: <CAOysbxpcKiGRj3Dvb9CyRW1UABRCX0skmCyZa8vugbbsLrwoAA@mail.gmail.com> (raw)
In-Reply-To: <OFB88811EF.D6B426D3-ONC1257E85.0047E0C7-C1257E85.004F1301@pl.ibm.com>
Cześć Angela,
Make sure your NIC is configured properly as described in this thread:
http://dpdk.org/ml/archives/dev/2015-May/018096.html
Andriy
On Fri, Jul 17, 2015 at 4:23 PM, Angela Czubak <ACzubak@pl.ibm.com> wrote:
> Hi,
>
> I have some difficulties using ip checksum tx offload capabilities - I
> think I set everything as advised by the API documentation, but
> unfortunately the packet leaves the interface with its ip checksum still
> being zero (it reaches its destination).
>
> What I do is:
> buffer->ol_flags |= PKT_TX_IP_CKSUM|PKT_TX_IPV4;
> ip_header->hdr_checksum = 0;
> buffer->l3_len = sizeof(struct ipv4_hdr);
> buffer->l2_len = sizeof(struct ether_hdr);
>
> In L4 there's UDP, which checksum is zeroed if that matters.
>
> Is there something I am missing? The NIC is Intel Corporation Ethernet
> Controller X710 for 10GbE SFP+ (rev 01).
>
> What is more, is there any particular reason for assuming in
> i40e_xmit_pkts that offloading checksums is unlikely (I mean the line no
> 1307 "if (unlikely(ol_flags & I40E_TX_CKSUM_OFFLOAD_MASK))" at
> dpdk-2.0.0/lib/librte_pmd_i40e/i40e_rxtx.c)?
>
> Regards,
> Angela
--
Andriy Berestovskyy
next prev parent reply other threads:[~2015-07-17 14:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 14:23 Non-working TX IP checksum offload Angela Czubak
2015-07-17 14:37 ` Andriy Berestovskyy [this message]
2015-07-21 13:11 ` Angela Czubak
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=CAOysbxpcKiGRj3Dvb9CyRW1UABRCX0skmCyZa8vugbbsLrwoAA@mail.gmail.com \
--to=aber@semihalf.com \
--cc=ACzubak@pl.ibm.com \
--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
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).