[dpdk-dev] [PATCH v2 00/17] prepare for rte_device / rte_driver

2016-06-16 Thread Jan Viktorin
orin at > > rehivetech.com; > > dev at dpdk.org; Iremonger, Bernard > > Subject: Re: [dpdk-dev] [PATCH v2 00/17] prepare for rte_device / rte_driver > > > > 2016-06-16 06:32, Shreyansh Jain: > > > From: dev [mailto:dev-bounces at dpdk.org] On Behalf O

[dpdk-dev] [PATCH v2 00/17] prepare for rte_device / rte_driver

2016-06-16 Thread Jan Viktorin
On Thu, 16 Jun 2016 11:19:59 +0200 Thomas Monjalon wrote: > 2016-06-16 10:23, Jan Viktorin: > > I think, we should consider to move it to somebody else. I would work on > > it, however, I don't see all the tasks that are to be done. That's why I > > was waiting to finalize those patchs by

[dpdk-dev] [PATCH v2 00/17] prepare for rte_device / rte_driver

2016-06-16 Thread Thomas Monjalon
2016-06-16 10:23, Jan Viktorin: > I think, we should consider to move it to somebody else. I would work on it, > however, I don't see all the tasks that are to be done. That's why I was > waiting to finalize those patchs by David or Thomas. For me, the important > things were to generalize

[dpdk-dev] [PATCH v2 00/17] prepare for rte_device / rte_driver

2016-06-16 Thread Jan Viktorin
patchset). What more? Jan?Viktorin RehiveTech Sent?from?a?mobile?device ? P?vodn? zpr?va ? Od: Thomas Monjalon Odesl?no: ?tvrtek, 16. ?ervna 2016 9:34 Komu: Shreyansh Jain Kopie: David Marchand; viktorin at rehivetech.com; dev at dpdk.org; Iremonger, Bernard P?edm?t: Re: [dpdk-dev] [PATCH v2 00/17

[dpdk-dev] [PATCH v2 00/17] prepare for rte_device / rte_driver

2016-06-16 Thread Shreyansh Jain
Hi, > -Original Message- > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] > Sent: Thursday, June 16, 2016 1:04 PM > To: Shreyansh Jain > Cc: David Marchand ; viktorin at rehivetech.com; > dev at dpdk.org; Iremonger, Bernard > Subject: Re: [dpdk-dev] [PA

[dpdk-dev] [PATCH v2 00/17] prepare for rte_device / rte_driver

2016-06-16 Thread Shreyansh Jain
thomas.monjalon at 6wind.com; viktorin at rehivetech.com > > Subject: [dpdk-dev] [PATCH v2 00/17] prepare for rte_device / rte_driver > > > > Following discussions with Jan [1] and some cleanup I started on pci code, > > here is a patchset that reworks pdev drivers regist

[dpdk-dev] [PATCH v2 00/17] prepare for rte_device / rte_driver

2016-06-16 Thread Thomas Monjalon
2016-06-16 06:32, Shreyansh Jain: > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Iremonger, Bernard > > Patches 3,8,16 and 17 no longer apply to the latest master branch. > > A rebase is needed. > > With the recent most head (04920e6): 01, 03, 08, 15, 16 and 17 are failing. > > Just

[dpdk-dev] [PATCH v2 00/17] prepare for rte_device / rte_driver

2016-05-27 Thread Iremonger, Bernard
Hi David, > -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of David Marchand > Sent: Wednesday, April 20, 2016 12:44 PM > To: dev at dpdk.org > Cc: thomas.monjalon at 6wind.com; viktorin at rehivetech.com > Subject: [dpdk-dev] [PATCH

[dpdk-dev] [PATCH v2 00/17] prepare for rte_device / rte_driver

2016-05-06 Thread Jan Viktorin
Hello, On Fri, 6 May 2016 10:26:45 +0100 Declan Doherty wrote: > On 20/04/16 13:41, Jan Viktorin wrote: > > On Wed, 20 Apr 2016 13:05:24 +0100 > > Bruce Richardson wrote: > > > >> On Wed, Apr 20, 2016 at 01:44:00PM +0200, David Marchand wrote: > >>> Following discussions with Jan [1] and

[dpdk-dev] [PATCH v2 00/17] prepare for rte_device / rte_driver

2016-05-06 Thread Declan Doherty
On 20/04/16 13:41, Jan Viktorin wrote: > On Wed, 20 Apr 2016 13:05:24 +0100 > Bruce Richardson wrote: > >> On Wed, Apr 20, 2016 at 01:44:00PM +0200, David Marchand wrote: >>> Following discussions with Jan [1] and some cleanup I started on pci code, >>> here is a patchset that reworks pdev

[dpdk-dev] [PATCH v2 00/17] prepare for rte_device / rte_driver

2016-04-22 Thread Jan Viktorin
[...] > > > > > > Changes since v1: > > > - rebased on HEAD, new drivers should be okay > > > - patches have been split into smaller pieces > > > - RTE_INIT macro has been added, but in the end, I am not sure it is > > > useful > > > - device type has been removed from ethdev, as it was used

[dpdk-dev] [PATCH v2 00/17] prepare for rte_device / rte_driver

2016-04-20 Thread Jan Viktorin
On Wed, 20 Apr 2016 13:05:24 +0100 Bruce Richardson wrote: > On Wed, Apr 20, 2016 at 01:44:00PM +0200, David Marchand wrote: > > Following discussions with Jan [1] and some cleanup I started on pci code, > > here is a patchset that reworks pdev drivers registration and hotplug api. > > > > The

[dpdk-dev] [PATCH v2 00/17] prepare for rte_device / rte_driver

2016-04-20 Thread David Marchand
Following discussions with Jan [1] and some cleanup I started on pci code, here is a patchset that reworks pdev drivers registration and hotplug api. The structures changes mentioned in [1] are still to be done, but at least, I think we are one step closer to it. Before this patchset, rte_driver

[dpdk-dev] [PATCH v2 00/17] prepare for rte_device / rte_driver

2016-04-20 Thread Bruce Richardson
On Wed, Apr 20, 2016 at 01:44:00PM +0200, David Marchand wrote: > Following discussions with Jan [1] and some cleanup I started on pci code, > here is a patchset that reworks pdev drivers registration and hotplug api. > > The structures changes mentioned in [1] are still to be done, but at least,