On 10/13/2017 12:15 AM, Pavan Nikhilesh wrote:
When event Rx adapter uses software based packet transfer, event op is always RTE_EVENT_OP_NEW. By using rte_event_enqueue_new_burst API the underlying event devices driver can use it as a hint to optimize enqueue operation if possible.Signed-off-by: Pavan Nikhilesh <pbhagavat...@caviumnetworks.com> --- lib/librte_eventdev/rte_event_eth_rx_adapter.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/librte_eventdev/rte_event_eth_rx_adapter.c b/lib/librte_eventdev/rte_event_eth_rx_adapter.c index 1e42dde..fcba18d 100644 --- a/lib/librte_eventdev/rte_event_eth_rx_adapter.c +++ b/lib/librte_eventdev/rte_event_eth_rx_adapter.c @@ -392,7 +392,7 @@ flush_event_buffer(struct rte_event_eth_rx_adapter *rx_adapter) &rx_adapter->event_enqueue_buffer; struct rte_event_eth_rx_adapter_stats *stats = &rx_adapter->stats;- uint16_t n = rte_event_enqueue_burst(rx_adapter->eventdev_id,+ uint16_t n = rte_event_enqueue_new_burst(rx_adapter->eventdev_id, rx_adapter->event_port_id, buf->events, buf->count);
Reviewed-by: Nikhil Rao <nikhil....@intel.com>
