DPDK usage discussions
 help / color / mirror / Atom feed
From: Long Li <longli@microsoft.com>
To: Nandini Rangaswamy <nandini.rangaswamy@broadcom.com>,
	Stephen Hemminger <stephen@networkplumber.org>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: RE: Netvsc PMD : Hotplug handling : checksum offloads
Date: Thu, 31 Oct 2024 22:14:53 +0000	[thread overview]
Message-ID: <CYYPR21MB40225ECDD89214F28E1FBE8FCE552@CYYPR21MB4022.namprd21.prod.outlook.com> (raw)
In-Reply-To: <CAAkQrK--eqSu7WBy9coAxS42HoD-dtOxNuLBHL+2EcGFxfK5ZQ@mail.gmail.com>

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

Hi Nandini,

Just want to clarify, you don’t use TX checksum with Netvsc but the packet is sent to the wire with checksum automatically set.

If you use TX/RX checksum with Netvsc, do you see problems while sending/receiving packets with the correct checksums?

VF should always use the same checksum offload settings as Netvsc, it is done in hn_vf_add().  Unless you have a special requirement, you probably don’t want to handle hotplug events for the VF, as Netvsc should handle that for you. You should always use Netvsc to send/receive all packets.

Thanks,
Long


From: Nandini Rangaswamy <nandini.rangaswamy@broadcom.com>
Sent: Tuesday, October 29, 2024 6:02 PM
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Long Li <longli@microsoft.com>; users@dpdk.org
Subject: Re: Netvsc PMD : Hotplug handling : checksum offloads

Hi Stephen,
I am testing UDP IPv4 offloads. Earlier with failsafe PMD , my dpdk app would subscribe to hotplug add and delete callbacks. In Hotplug add callback the appropriate mbuf flags were set for hardware to perform checksum offload and in hotplug delete, the function pointer was modified to calculate checksum in software.
To test netvsc PMD, I have commented out the code in hotplug callbacks to understand what happens. As you mentioned, as part of hotplug add, hn_vf_add restores all the VF offloads and it works as expected. In case of hotplug removal, I notice that even in the absence of software checksum , the packets are reaching the destination with the correct checksum. The dpdk app continues to set mbuf flags for offload in the sender. I expected packets to be dropped at the sender because offloads should be absent as VF is removed. Does netvsc pmd calculate checksum if mbuf checksum offload flags are set and VF is absent?

Regards,
Nandini

On Thu, Oct 24, 2024 at 2:38 PM Nandini Rangaswamy <nandini.rangaswamy@broadcom.com<mailto:nandini.rangaswamy@broadcom.com>> wrote:
Hi Stephen/Long,
I did some more code instrumentation and I observed that when a hotplug add event is received, the conf is applied back to VF and offloads work as expected.
I also observe that when VF is removed, the offloads still continue to work as expected. Is this because the offloads are not unset when VF is removed ?
Regards,
Nandini

On Thu, Oct 24, 2024 at 9:33 AM Stephen Hemminger <stephen@networkplumber.org<mailto:stephen@networkplumber.org>> wrote:
On Wed, 23 Oct 2024 13:34:53 -0700
Nandini Rangaswamy <nandini.rangaswamy@broadcom.com<mailto:nandini.rangaswamy@broadcom.com>> wrote:

> Hi Stephen,
> The code looking at checksum flags in each packet would not give us desired
> performance. Instead, should the dpdk app register callbacks for hotplug
> add and re-configure the checksum offloads when VF is added again?
> Regards,
> Nandini

The code in hn_vf_add which is where netvsc PMD handles hot add of VF
should be feeding the current offload settings to the VF.

Maybe the rte_eth_conf being passed to VF is incorrect, or
the configuration step there is failing. Probably need more instrumentation
and logs to tell.

This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it.

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

      reply	other threads:[~2024-10-31 22:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-19 18:11 Nandini Rangaswamy
2024-09-19 18:47 ` Stephen Hemminger
2024-10-23 20:34   ` Nandini Rangaswamy
2024-10-24 16:33     ` Stephen Hemminger
2024-10-24 21:38       ` Nandini Rangaswamy
2024-10-30  1:01         ` Nandini Rangaswamy
2024-10-31 22:14           ` Long Li [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=CYYPR21MB40225ECDD89214F28E1FBE8FCE552@CYYPR21MB4022.namprd21.prod.outlook.com \
    --to=longli@microsoft.com \
    --cc=nandini.rangaswamy@broadcom.com \
    --cc=stephen@networkplumber.org \
    --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).