title: Order of network ports (portid's) in a dpdk application
body: <p>In my dpdk application, I want to use three network interfaces, two PCI and one tap interface. The below are the parameters that I'm passing to my dpdk application:</p>
  <p>--vdev=net_tap0,mac=fixed -a '00:08.0' -a '00:09.0'</p>
  <p>Is there a way to know which portid's they map to without starting the dpdk application. More specifically, what is the order in which dpdk assigns portid's to the interfaces?</p>
  <p>EDIT: I ran the <code>dpdk-proc-info</code> program as suggested and got the below error report:</p>
  <pre><code>EAL: RTE Version: 'DPDK 20.11.1'
  EAL: failed to send to (/var/run/dpdk/rte/mp_socket) due to Connection refused
  EAL: Fail to send request /var/run/dpdk/rte/mp_socket:bus_vdev_mp vdev_scan(): Failed to request vdev from primary
  EAL: failed to send to (/var/run/dpdk/rte/mp_socket) due to Connection refused
  EAL: Fail to send request /var/run/dpdk/rte/mp_socket:eal_vfio_mp_sync
  EAL:   cannot request default container fd
  EAL: VFIO support could not be initialized
  EAL:   Invalid NUMA socket, default to 0
  EAL:   Invalid NUMA socket, default to 0
  EAL: Requested device 0000:00:08.0 cannot be used
  EAL:   Invalid NUMA socket, default to 0
  EAL: Requested device 0000:00:09.0 cannot be used
  EAL: No legacy callbacks, legacy socket not created
  EAL: Error - exiting with code: 1   Cause: No primary DPDK process is running.
  </code></pre>
  <p>From the above error report, it appears that a dpdk app needs to be running first to use <code>dpdk-proc-info</code></p>