From: Nandini Rangaswamy <nandini.rangaswamy@broadcom.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Long Li <longli@microsoft.com>, users@dpdk.org
Subject: Re: Netvsc PMD : Hotplug handling : checksum offloads
Date: Thu, 24 Oct 2024 14:38:53 -0700 [thread overview]
Message-ID: <CAAkQrK8OeC9p1TE2Cwsme7F13XN5=w5b=reL2MBOSMZ7OFmBpg@mail.gmail.com> (raw)
In-Reply-To: <20241024093357.2473c767@hermes.local>
[-- Attachment #1: Type: text/plain, Size: 1933 bytes --]
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> wrote:
> On Wed, 23 Oct 2024 13:34:53 -0700
> Nandini Rangaswamy <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: 2425 bytes --]
next prev parent reply other threads:[~2024-10-24 21:39 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 [this message]
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='CAAkQrK8OeC9p1TE2Cwsme7F13XN5=w5b=reL2MBOSMZ7OFmBpg@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).