On 8/10/2017 10:23 PM, Jerin Jacob wrote:
-----Original Message-----
Date: Wed, 9 Aug 2017 19:24:30 +0000
From: "Eads, Gage" <gage.e...@intel.com>
Makes sense. Are you thinking the helper function would do stop + reconfig with
additional port + start + setup port, or just setup the port with an ID the app
supplies (only when a port is required, of course)? The second one could be done with
little additional code -- the app just needs to check if an additional port is needed
when configuring the eventdev, and another helper function could take a list of
<eventdev, ethdev> pairs and return true if any don't have an inbuilt port.
I am in favor adding more logic in helper function(I believe, first one ) so
that it will help
application reuse the helper functions for the normal case.
Hi Jerin,
My understanding of the discussion above is that the simple API adapter
creation API is
int rte_event_eth_rx_adapter_create(id, eventdev_id)
And the raw API is
typedef int (*rx_adapter_conf_cb) (id, eventdev_id,
struct rte_event_eth_rx_adapter_conf *conf, void *arg);
struct rte_event_eth_rx_adapter_conf {
uint8_t rx_event_port_id;
uint32_t max_nb_rx;
};
int rte_event_eth_rx_adapter_create_ext(id, eventdev_id, conf_cb,
conf_arg)
The conf_cb is invoked if the rte_event_eth_rx_adapter_conf struct needs
to be filled out. the _create_ext() API is used internally by
rte_event_eth_rx_adapter_create()
Does that look OK to you ?
Nikhil
