On 7/11/2018 11:46 PM, Stephen Hemminger wrote:
On Wed, 11 Jul 2018 18:41:50 +0800
Jeff Guo <[email protected]> wrote:
As we know, hot plug is an importance feature, either use for the datacenter
device’s fail-safe, or use for SRIOV Live Migration in SDN/NFV. It could bring
the higher flexibility and continuality to the networking services in multiple
use cases in industry. So let we see, dpdk as an importance networking
framework, what can it help to implement hot plug solution for users.
We already have a general device event detect mechanism, failsafe driver,
bonding driver and hot plug/unplug api in framework, app could use these to
develop their hot plug solution.
I like seeing a better solution to hot plug. But it is worth mentioning
that for the Hyper-V netvsc driver this is mostly unnecessary. The Hyper-V
host notifies the network driver directly about availability of SRIOV
device, and the netvsc device driver can use that to do its own VF
management. It doesn't really need (or want) to be using a general
PCI solution.
I am not sure about Hyper-v netvsc driver, but i am very interesting to
deep analyze it to find what could let we find a best solution for
hotplug. But since some customer, who like me still not have chance to
use Hyper-v, they will encounter the hotplug issue when use kvm or other
platform.
so let we said that the topic about here is aim to fix the issue for
that part of customer or developer. Just let hotplug be used more in
diversity scenario.
