* ``representor`` for a device which supports the creation of representor ports
this argument allows user to specify which switch ports to enable port
- representors for.::
-
- -w DBDF,representor=0
- -w DBDF,representor=[0,4,6,9]
- -w DBDF,representor=[0-31]
+ representors for. Multiple representors in one device argument is invalid::
+
+ -a DBDF,representor=vf0
+ -a DBDF,representor=vf[0,4,6,9]
+ -a DBDF,representor=vf[0-31]
+ -a DBDF,representor=vf[0,2-4,7,9-11]
+ -a DBDF,representor=sf0
+ -a DBDF,representor=sf[1,3,5]
+ -a DBDF,representor=sf[0-1023]
+ -a DBDF,representor=sf[0,2-4,7,9-11]
+ -a DBDF,representor=pf1vf0
+ -a DBDF,representor=pf[0-1]sf[0-127]
+ -a DBDF,representor=pf1
Note: PMDs are not required to support the standard device arguments and users
should consult the relevant PMD documentation to see support devargs.
For example when PF is reset, the PF sends a message to notify VFs of
this event and also trigger an interrupt to VFs. Then in the interrupt
service routine the VFs detects this notification message and calls
-_rte_eth_dev_callback_process(dev, RTE_ETH_EVENT_INTR_RESET, NULL).
+rte_eth_dev_callback_process(dev, RTE_ETH_EVENT_INTR_RESET, NULL).
This means that a PF reset triggers an RTE_ETH_EVENT_INTR_RESET
-event within VFs. The function _rte_eth_dev_callback_process() will
+event within VFs. The function rte_eth_dev_callback_process() will
call the registered callback function. The callback function can trigger
the application to handle all operations the VF reset requires including
stopping Rx/Tx queues and calling rte_eth_dev_reset().