On 09/01/2018 22:01, Ferruh Yigit wrote:
<...>
The port representor infrastructure is enabled through a single common, device
independent, virtual PMD whos context is initialized and enabled through a
broker instance running within the context of the physical function device
driver.>
+-------------------------+ +-------------------------+
| rte_ethdev | | rte_ethdev |
+-------------------------+ +-------------------------+
| Physical Function PMD | | Port Reperesentor PMD |
| +-------------+ | | +---------+ +---------+ |
| | Representor | | | | dev_data| | dev_ops | |
| | Broker | | | +----+----+ +----+----+ |
| | +---------+ | | +------|-----------|------+
| | | VF Port | | | | |
| | | Context +------------------+ |
| | +---------+ | | |
| | +---------+ | | |
| | | Handler +------------------------------+
| | | Ops | | |
| | +---------+ | |
| +-------------+ |
+-------------------------+
Creation of representor ports can be achieved either through the --vdev EAL
option or through the rte_vdev_init() API. Each port representor requires the
BDF of it's parent PF and the Virtual Function ID of the port which the
representor will support. During initialization of the representor PMD, it calls
the broker API to register itself with the PF PMD and to get it's context
configured which includes the setting up of it's context and ops function
handlers.
Above no more true, right?
Right. We will rewrite these parts.
