On Thu, Feb 02, 2017 at 11:19:51AM +0000, Nipun Gupta wrote:

quoted

-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Jerin Jacob
Sent: Wednesday, December 21, 2016 14:55
To: dev@dpdk.org
Cc: thomas.monjalon@6wind.com; bruce.richardson@intel.com; Hemant
Agrawal [off-list ref]; gage.eads@intel.com;
harry.van.haaren@intel.com; Jerin Jacob [off-list ref]
Subject: [dpdk-dev] [PATCH v4 2/6] eventdev: define southbound driver
interface

Signed-off-by: Jerin Jacob <redacted>
Acked-by: Bruce Richardson <redacted>
---
 lib/librte_eventdev/rte_eventdev.h     |  38 +++++
 lib/librte_eventdev/rte_eventdev_pmd.h | 294
+++++++++++++++++++++++++++++++++
 2 files changed, 332 insertions(+)
 create mode 100644 lib/librte_eventdev/rte_eventdev_pmd.h

<snip>

quoted

+typedef int (*eventdev_port_link_t)(void *port,
+		const uint8_t queues[], const uint8_t priorities[],
+		uint16_t nb_links);

I think having event device as input parameter to the port_link & port_unlink will
be required so that queue configuration can be fetched from the event device.

Or each port structure in each driver can have a pointer back to its
containing eventdev. That is what we have done in our SW eventdev
driver.

/Bruce