DPDK usage discussions
 help / color / mirror / Atom feed
From: "jiangheng (H)" <jiangheng12@huawei.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] DPDK RX TCP checksum failed
Date: Sat, 26 Mar 2022 08:13:21 +0000	[thread overview]
Message-ID: <cb53d6174669407b96a0f6a09d6bf134@huawei.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1142 bytes --]

Hi all,

I tried using the checksum offloads feature in DPDK and it did not see working under virtual machine.

Port only support TCP checksum and do not support IP checksum:
rx_offload_capa = DEV_RX_OFFLOAD_TCP_CKSUM
tx_offload_capa = DEV_TX_OFFLOAD_TCP_CKSUM

so I config rxmode.offload txmode.offloads as below:
rxmode.offloads = DEV_RX_OFFLOAD_TCP_CKSUM
txmode.offloads = DEV_TX_OFFLOAD_TCP_CKSUM

For TX, I set the following parameters, it works good.
mbuf->l2_len = sizeof(*ethhdr)
mbuf->l3_len = ip header len
mbuf-ol_flags = RTE_MBUF_F_TX_IPV4 | RTE_MBUF_F_TX_TCP_CKSUM


For RX, It will execute the following code:
In drivers/net/virtio/virtio_rxtx.c  virtio_rx_offload function :
    if (hdr->flags & VIRTIO_NET_HDR_F_NEEDS_CSUM) {
        hdrlen = hdr_lens.l2_len + hdr_lens.l3_len + hdr_lens.l4_len;
        if (hdr->csum_start <= hdrlen && l4_supported) {
            m->ol_flags |= RTE_MBUF_F_RX_L4_CKSUM_NONE;
        } else {

m->ol_flags set to RTE_MBUF_F_RX_L4_CKSUM_NONE, causing the TCP RX checksum failed.
How do I avoid the above code going into this branch?

Thanks,
Jinag.








[-- Attachment #2: Type: text/html, Size: 5709 bytes --]

             reply	other threads:[~2022-03-26  8:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-26  8:13 jiangheng (H) [this message]
2022-03-26 18:59 ` Stephen Hemminger
2022-03-28  1:50   ` 答复: " jiangheng (H)
2022-03-28  2:15     ` Harold Huang
2022-04-07 12:50       ` 答复: " jiangheng (H)
2022-03-28  3:11   ` fwefew 4t4tg
2022-04-07 13:42     ` 答复: " jiangheng (H)

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=cb53d6174669407b96a0f6a09d6bf134@huawei.com \
    --to=jiangheng12@huawei.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).