[dpdk-dev] [PATCH 1/9] pci: no need for dynamic tailq init

2016-02-08 Thread vikto...@rehivetech.com
On Fri, 29 Jan 2016 15:08:28 +0100 David Marchand wrote: > These lists can be initialized once and for all at build time. > With this, those lists are only manipulated in a common place > (and we could even make them private). > > A nice side effect is that pci drivers can now register in constr

[dpdk-dev] [PATCH 1/9] pci: no need for dynamic tailq init

2016-01-29 Thread David Marchand
These lists can be initialized once and for all at build time. With this, those lists are only manipulated in a common place (and we could even make them private). A nice side effect is that pci drivers can now register in constructors. Signed-off-by: David Marchand --- lib/librte_eal/bsdapp/ea

[dpdk-dev] [PATCH 1/9] pci: no need for dynamic tailq init

2016-01-22 Thread David Marchand
These lists can be initialized once and for all at build time. With this, those lists are only manipulated in a common place (and we could even make them private). Signed-off-by: David Marchand --- lib/librte_eal/bsdapp/eal/eal_pci.c| 3 --- lib/librte_eal/common/eal_common_pci.c | 6 --