DPDK usage discussions
 help / color / mirror / Atom feed
From: Nandini Rangaswamy <nandini.rangaswamy@broadcom.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: users@dpdk.org, longli@microsoft.com
Subject: Re: Query regarding netvsc PMD : VF removal
Date: Thu, 25 Jul 2024 11:41:59 -0700	[thread overview]
Message-ID: <CAAkQrK-VCBwocF0cD8f15iLZqhRoWtuOUDBaPnvUc563dF7vtQ@mail.gmail.com> (raw)
In-Reply-To: <20240725111138.6cb22b5c@hermes.local>

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

Hi Stephen,
I am using the DPDK 22.11.5 LTS. Should the DPDK code take care of
unbinding synthetic interface from uio_hv_generic or should it be done by
the app when it gets hotplug notification?
Regards,
Nandini

On Thu, Jul 25, 2024 at 11:11 AM Stephen Hemminger <
stephen@networkplumber.org> wrote:

> On Thu, 25 Jul 2024 10:52:18 -0700
> Nandini Rangaswamy <nandini.rangaswamy@broadcom.com> wrote:
>
> > Hi,
> > I am integrating my DPDK app (using DPDK version 22.11) with Netvsc PMD.
> I
> > was testing the use case of VF removal with the DPDK app.
> > I registered for hotplug notification in the DPDK app and enabled DPDK
> > logs. I see the APIs being invoked for VF removal from the logs below:
>
> Make sure you are using the updated 22.11 LTS release.
>

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

  reply	other threads:[~2024-07-25 18:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-25 17:52 Nandini Rangaswamy
2024-07-25 18:11 ` Stephen Hemminger
2024-07-25 18:41   ` Nandini Rangaswamy [this message]
2024-07-25 21:52     ` Stephen Hemminger
2024-07-26 22:45       ` Nandini Rangaswamy
2024-07-27  1:14         ` Long Li
2024-08-05 21:52           ` Nandini Rangaswamy

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=CAAkQrK-VCBwocF0cD8f15iLZqhRoWtuOUDBaPnvUc563dF7vtQ@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).