DPDK usage discussions
 help / color / mirror / Atom feed
From: "Aisenur Yoldaş" <aisenur.yoldas@b-ulltech.com>
To: "users@dpdk.org" <users@dpdk.org>
Cc: "Volkan Atlı" <volkan.atli@b-ulltech.com>,
	"Denis Davidoglu" <denis.davidoglu@b-ulltech.com>
Subject: DPDK 23.11 VMware checksum offload
Date: Thu, 24 Apr 2025 23:04:31 +0000	[thread overview]
Message-ID: <DB9P190MB1066B4DF6EA8931CD2583897C0AA2@DB9P190MB1066.EURP190.PROD.OUTLOOK.COM> (raw)

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

Hi,

I am trying to use dpdk 23.11 on a VMware virtual machine for a forwarding application. My quest OS is Ubuntu 22.04 LTS and I am using the e1000 network card. I realized checksums of the processed packets are not correct when using checksum offload feature of DPDK. I suspect that checksums are stay same when packets are changed.

I also tried using vmxnet3 NIC in virtual machine but I got the same result. I was using same code on a Mellanox card before on a real hardware and it was working fine.  When I calculated the checksum in the code instead of offloading it is working, but I would like to use the offloading feature. What do you think could be the cause for this problem.

The configuration I am using for checksum offload is:

        struct rte_eth_conf port_conf = {
            .rxmode = {
                .mq_mode = RTE_ETH_MQ_RX_RSS,
            },
            .txmode = {
                .offloads =
                    RTE_ETH_TX_OFFLOAD_IPV4_CKSUM  |
                    RTE_ETH_TX_OFFLOAD_UDP_CKSUM   |
                    RTE_ETH_TX_OFFLOAD_TCP_CKSUM  ,
                    .mq_mode = RTE_ETH_MQ_TX_NONE,
            },

For vmxnet3 however I didn't use RTE_ETH_TX_OFFLOAD_IPV4_CKSUM because apparently that driver is not supporting IPv4 offload.

Thanks

Best,

Aisenur

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

                 reply	other threads:[~2025-04-24 23:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=DB9P190MB1066B4DF6EA8931CD2583897C0AA2@DB9P190MB1066.EURP190.PROD.OUTLOOK.COM \
    --to=aisenur.yoldas@b-ulltech.com \
    --cc=denis.davidoglu@b-ulltech.com \
    --cc=users@dpdk.org \
    --cc=volkan.atli@b-ulltech.com \
    /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).