From: "Guo, Junfeng" <junfeng.guo@intel.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>,
Levend Sayar <levendsayar@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Jeroen de Borst <jeroendb@google.com>,
Rushil Gupta <rushilg@google.com>,
Jordan Kimbrough <jrkim@google.com>
Subject: RE: Google Virtual NIC (GVE) PMD
Date: Tue, 31 Jan 2023 06:52:30 +0000 [thread overview]
Message-ID: <DM6PR11MB37231B91661145BCD3B4721DE7D09@DM6PR11MB3723.namprd11.prod.outlook.com> (raw)
In-Reply-To: <fb5ab153-7313-e4c3-85c3-b462fffe4a11@amd.com>
> -----Original Message-----
> From: Ferruh Yigit <ferruh.yigit@amd.com>
> Sent: Wednesday, January 18, 2023 23:32
> To: Levend Sayar <levendsayar@gmail.com>; Guo, Junfeng
> <junfeng.guo@intel.com>
> Cc: dev@dpdk.org; Jeroen de Borst <jeroendb@google.com>; Rushil
> Gupta <rushilg@google.com>; Jordan Kimbrough <jrkim@google.com>
> Subject: Re: Google Virtual NIC (GVE) PMD
>
> On 1/18/2023 1:47 PM, Levend Sayar wrote:
> > Hi all.
> >
> > PMD for Google Virtual NIC says it is capable of IPV4 TX checksum
> > offloading.
> >
> >
> https://github.com/DPDK/dpdk/blob/main/drivers/net/gve/gve_ethdev.c
> #L285
> >
> <https://github.com/DPDK/dpdk/blob/main/drivers/net/gve/gve_ethdev.
> c#L285>
> >
> > But according to my tests on Google Cloud, it is not doing that ipv4
> > checksum tx offload.
> > I only managed to send a packet via DPDK if I calculate the checksum
> myself.
> >
> > Do you have any idea about that?
Thanks for the feedback!
I tried to use this loopback typo in csum fwd mode based on this doc:
"https://doc.dpdk.org/dts/test_plans/checksum_offload_test_plan.html"
During the dpdk ports forwarding, the received pkts at tester side can have
correct csum after setting with 'csum set ip hw 0'.
Also, on GCP, the gateway between VMs will correct the wrong L3 chksum
values by default when passing the pkts.
Could you please provide more details for your test cases?
So that we can have more information to verify this. Thanks!
> >
>
> cc'ed gve maintainers.
Thanks Ferruh for the forwarding!
next prev parent reply other threads:[~2023-01-31 6:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 13:47 Levend Sayar
2023-01-18 15:31 ` Ferruh Yigit
2023-01-31 6:52 ` Guo, Junfeng [this message]
2023-01-31 8:17 ` Levend Sayar
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=DM6PR11MB37231B91661145BCD3B4721DE7D09@DM6PR11MB3723.namprd11.prod.outlook.com \
--to=junfeng.guo@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=jeroendb@google.com \
--cc=jrkim@google.com \
--cc=levendsayar@gmail.com \
--cc=rushilg@google.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).