[dpdk-dev] [PATCH 03/15] pmd: Add PMD_REGISTER_DRIVER macro

2014-04-18 Thread Thomas Monjalon
2014-04-18 09:20, Neil Horman: > On Fri, Apr 18, 2014 at 02:08:56PM +0200, Thomas Monjalon wrote: > > 2014-04-18 08:04, Neil Horman: > > > On Fri, Apr 18, 2014 at 04:42:01AM -0700, Thomas Monjalon wrote: > > > > 2014-04-15 14:05, Neil Horman: > > > > > Rather than have each driver have to remember

[dpdk-dev] [PATCH 03/15] pmd: Add PMD_REGISTER_DRIVER macro

2014-04-18 Thread Thomas Monjalon
2014-04-18 08:04, Neil Horman: > On Fri, Apr 18, 2014 at 04:42:01AM -0700, Thomas Monjalon wrote: > > 2014-04-15 14:05, Neil Horman: > > > Rather than have each driver have to remember to add a constructor to it > > > to > > > make sure its gets registered properly, wrap that process up in a macro

[dpdk-dev] [PATCH 03/15] pmd: Add PMD_REGISTER_DRIVER macro

2014-04-18 Thread Neil Horman
On Fri, Apr 18, 2014 at 03:32:15PM +0200, Thomas Monjalon wrote: > 2014-04-18 09:20, Neil Horman: > > On Fri, Apr 18, 2014 at 02:08:56PM +0200, Thomas Monjalon wrote: > > > 2014-04-18 08:04, Neil Horman: > > > > On Fri, Apr 18, 2014 at 04:42:01AM -0700, Thomas Monjalon wrote: > > > > > 2014-04-15 1

[dpdk-dev] [PATCH 03/15] pmd: Add PMD_REGISTER_DRIVER macro

2014-04-18 Thread Neil Horman
On Fri, Apr 18, 2014 at 02:08:56PM +0200, Thomas Monjalon wrote: > 2014-04-18 08:04, Neil Horman: > > On Fri, Apr 18, 2014 at 04:42:01AM -0700, Thomas Monjalon wrote: > > > 2014-04-15 14:05, Neil Horman: > > > > Rather than have each driver have to remember to add a constructor to it > > > > to > >

[dpdk-dev] [PATCH 03/15] pmd: Add PMD_REGISTER_DRIVER macro

2014-04-18 Thread Neil Horman
On Fri, Apr 18, 2014 at 04:42:01AM -0700, Thomas Monjalon wrote: > 2014-04-15 14:05, Neil Horman: > > Rather than have each driver have to remember to add a constructor to it to > > make sure its gets registered properly, wrap that process up in a macro to > > make registration a one line affair.

[dpdk-dev] [PATCH 03/15] pmd: Add PMD_REGISTER_DRIVER macro

2014-04-18 Thread Thomas Monjalon
2014-04-15 14:05, Neil Horman: > Rather than have each driver have to remember to add a constructor to it to > make sure its gets registered properly, wrap that process up in a macro to > make registration a one line affair. This also sets the stage for us to > make registration of vdev pmds and p

[dpdk-dev] [PATCH 03/15] pmd: Add PMD_REGISTER_DRIVER macro

2014-04-17 Thread Olivier MATZ
Hi Neil, On 04/16/2014 07:29 PM, Neil Horman wrote: > Ok, so look it up. DPDK is open source and cscope is easy to use. A > module initilization macro is a common method for doing init time binding in > modular programming (the best examples are the module_init() and module_exit() > macros in th

[dpdk-dev] [PATCH 03/15] pmd: Add PMD_REGISTER_DRIVER macro

2014-04-17 Thread Neil Horman
On Thu, Apr 17, 2014 at 10:08:29AM +0200, Olivier MATZ wrote: > Hi Neil, > > On 04/16/2014 07:29 PM, Neil Horman wrote: > >Ok, so look it up. DPDK is open source and cscope is easy to use. A > >module initilization macro is a common method for doing init time binding in > >modular programming (t

[dpdk-dev] [PATCH 03/15] pmd: Add PMD_REGISTER_DRIVER macro

2014-04-16 Thread Olivier MATZ
Hi Neil, On 04/16/2014 03:08 PM, Neil Horman wrote: > On Wed, Apr 16, 2014 at 01:52:49PM +0200, Thomas Monjalon wrote: >> 2014-04-15 14:05, Neil Horman: >>> Rather than have each driver have to remember to add a constructor to it to >>> make sure its gets registered properly, wrap that process up

[dpdk-dev] [PATCH 03/15] pmd: Add PMD_REGISTER_DRIVER macro

2014-04-16 Thread Thomas Monjalon
2014-04-15 14:05, Neil Horman: > Rather than have each driver have to remember to add a constructor to it to > make sure its gets registered properly, wrap that process up in a macro to > make registration a one line affair. This also sets the stage for us to > make registration of vdev pmds and p

[dpdk-dev] [PATCH 03/15] pmd: Add PMD_REGISTER_DRIVER macro

2014-04-16 Thread Neil Horman
On Wed, Apr 16, 2014 at 06:11:32PM +0200, Olivier MATZ wrote: > Hi Neil, > > On 04/16/2014 03:08 PM, Neil Horman wrote: > >On Wed, Apr 16, 2014 at 01:52:49PM +0200, Thomas Monjalon wrote: > >>2014-04-15 14:05, Neil Horman: > >>>Rather than have each driver have to remember to add a constructor to

[dpdk-dev] [PATCH 03/15] pmd: Add PMD_REGISTER_DRIVER macro

2014-04-16 Thread John W. Linville
On Wed, Apr 16, 2014 at 06:11:32PM +0200, Olivier MATZ wrote: > Hi Neil, > > On 04/16/2014 03:08 PM, Neil Horman wrote: > >On Wed, Apr 16, 2014 at 01:52:49PM +0200, Thomas Monjalon wrote: > >>2014-04-15 14:05, Neil Horman: > >>>Rather than have each driver have to remember to add a constructor to

[dpdk-dev] [PATCH 03/15] pmd: Add PMD_REGISTER_DRIVER macro

2014-04-16 Thread Neil Horman
On Wed, Apr 16, 2014 at 01:52:49PM +0200, Thomas Monjalon wrote: > 2014-04-15 14:05, Neil Horman: > > Rather than have each driver have to remember to add a constructor to it to > > make sure its gets registered properly, wrap that process up in a macro to > > make registration a one line affair.

[dpdk-dev] [PATCH 03/15] pmd: Add PMD_REGISTER_DRIVER macro

2014-04-16 Thread John W. Linville
On Wed, Apr 16, 2014 at 01:52:49PM +0200, Thomas Monjalon wrote: > 2014-04-15 14:05, Neil Horman: > > Rather than have each driver have to remember to add a constructor to it to > > make sure its gets registered properly, wrap that process up in a macro to > > make registration a one line affair.

[dpdk-dev] [PATCH 03/15] pmd: Add PMD_REGISTER_DRIVER macro

2014-04-15 Thread Neil Horman
Rather than have each driver have to remember to add a constructor to it to make sure its gets registered properly, wrap that process up in a macro to make registration a one line affair. This also sets the stage for us to make registration of vdev pmds and physical pmds a uniform process Signed-