DPDK usage discussions
 help / color / mirror / Atom feed
From: Nandini Rangaswamy <nandini.rangaswamy@broadcom.com>
To: Long Li <longli@microsoft.com>,
	Stephen Hemminger <stephen@networkplumber.org>,
	users@dpdk.org
Subject: Netvsc PMD : Hotplug handling : checksum offloads
Date: Thu, 19 Sep 2024 11:11:44 -0700	[thread overview]
Message-ID: <CAAkQrK9xTqiAXvURFmpjpgbpA+qyRNzBZ-4SnSAH2bUPBsJDhA@mail.gmail.com> (raw)

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

 Hi Long/Stephen,
I was going through the hotplug handling code in netvsc PMD and need
clarification.
Earlier with failsafe PMD , my dpdk app used to subscribe to hotplug events
to set the checksum offloads to do software checksum calculation when VF
was removed and switch to H/W checksum calculation when VF was added.
I see even with netvsc PMD , it does not do anything specific to RSS
/checksum offloads in hotplug callbacks but initializes VF port (through
ioctl) during hotplug add and removes VF port in hotplug remove callback.
So my understanding is, the dpdk app should continue to handle the checksum
offloads as part of hotplug callbacks and netvsc will not handle it
automatically.
Can you confirm if this is correct?
Regards,
Nandini

-- 
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: 1688 bytes --]

             reply	other threads:[~2024-09-19 18:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-19 18:11 Nandini Rangaswamy [this message]
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

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=CAAkQrK9xTqiAXvURFmpjpgbpA+qyRNzBZ-4SnSAH2bUPBsJDhA@mail.gmail.com \
    --to=nandini.rangaswamy@broadcom.com \
    --cc=longli@microsoft.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).