dpdk: fix device name suffix confusion with failsafe/netvsc 32/15732/2
authorStephen Hemminger <sthemmin@microsoft.com>
Mon, 5 Nov 2018 20:54:16 +0000 (12:54 -0800)
committerDamjan Marion <dmarion@me.com>
Tue, 6 Nov 2018 11:53:24 +0000 (11:53 +0000)
commitf286c4b9427748568036d04e8aa2408a4069dee7
tree7a1ce3804894b3befa9865ece8c9a28f73e8058b
parentef101310f4068abc61d43c1b08165c7a2018132d
dpdk: fix device name suffix confusion with failsafe/netvsc

When netvsc or failsafe DPDK device is used, the DPDK port id does not
match the VPP device instance id.  The code that formats the device
name was incorrectly calling DPDK device info using the VPP device
instance id. This causes the VPP interface to be named
"FortyGigabit0/2/0" based on mistakenly finding the PCI device
information of the hidden DPDK port id for the VF device.

Change-Id: I9366232f4b2087076bdcc1a58bf228007c24c084
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
src/plugins/dpdk/device/format.c