[dpdk-dev] [RFC PATCH 2/6] eal: introduce bus-device-driver structure

2016-11-17 Thread Shreyansh Jain
Hello Jan, Thanks for comments. Replies inline. On Thursday 17 November 2016 04:49 PM, Jan Blunck wrote: > On Thu, Nov 17, 2016 at 6:30 AM, Shreyansh Jain > wrote: >> A device is connected to a bus and services by a driver associated with >> the bus. It is responsibility of the bus to identify

[dpdk-dev] [RFC PATCH 2/6] eal: introduce bus-device-driver structure

2016-11-17 Thread Jan Blunck
On Thu, Nov 17, 2016 at 2:00 PM, Shreyansh Jain wrote: > > On Thursday 17 November 2016 04:49 PM, Jan Blunck wrote: >> >> On Thu, Nov 17, 2016 at 6:30 AM, Shreyansh Jain >> wrote: >>> >>> A device is connected to a bus and services by a driver associated with >>> the bus. It is responsibility of

[dpdk-dev] [RFC PATCH 2/6] eal: introduce bus-device-driver structure

2016-11-17 Thread Jan Blunck
On Thu, Nov 17, 2016 at 6:30 AM, Shreyansh Jain wrote: > A device is connected to a bus and services by a driver associated with > the bus. It is responsibility of the bus to identify the devices (scan) > and then assign each device to a matching driver. > > A PMD would allocate a rte_xxx_driver

[dpdk-dev] [RFC PATCH 2/6] eal: introduce bus-device-driver structure

2016-11-17 Thread Shreyansh Jain
A device is connected to a bus and services by a driver associated with the bus. It is responsibility of the bus to identify the devices (scan) and then assign each device to a matching driver. A PMD would allocate a rte_xxx_driver and rte_xxx_device. rte_xxx_driver has rte_driver and rte_bus embe