From: Ferruh Yigit <ferruh.yigit@xilinx.com>
To: <longli@linuxonhyperv.com>, <dev@dpdk.org>,
Stephen Hemminger <sthemmin@microsoft.com>
Cc: Long Li <longli@microsoft.com>, <stable@dpdk.org>
Subject: Re: [PATCH] net/netvsc: fix issues with hot adding multiple VF PCI devices
Date: Tue, 3 May 2022 11:01:09 +0100 [thread overview]
Message-ID: <5a26d4ef-e0f4-cfee-f4c2-b71febdcd381@xilinx.com> (raw)
In-Reply-To: <1648143977-18034-1-git-send-email-longli@linuxonhyperv.com>
On 3/24/2022 5:46 PM, longli@linuxonhyperv.com wrote:
> From: Long Li <longli@microsoft.com>
>
> This patch fixes two issues with hot removing/adding a VF PCI device:
> 1. The original device argument is lost when it's hot added
> 2. If there are multiple VFs hot adding at the same time, some of the VFs may
> not get added successfully because only one single VF status is stored in the
> netvsc.
>
> Fix these by storing the original device arguments and maintain a list of hot
> add contexts to deal with multiple VF devices.
>
> Fixes: a2a23a794b ("net/netvsc: support VF device hot add/remove")
> Cc: stable@dpdk.org
>
> Signed-off-by: Long Li <longli@microsoft.com>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2022-05-03 10:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 17:46 longli
2022-05-03 10:01 ` Ferruh Yigit [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=5a26d4ef-e0f4-cfee-f4c2-b71febdcd381@xilinx.com \
--to=ferruh.yigit@xilinx.com \
--cc=dev@dpdk.org \
--cc=longli@linuxonhyperv.com \
--cc=longli@microsoft.com \
--cc=stable@dpdk.org \
--cc=sthemmin@microsoft.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).