[dpdk-dev] API feature check _HAS_

2015-11-29 Thread Vlad Zolotarov
On 11/29/15 11:10, Gleb Natapov wrote: > On Sun, Nov 29, 2015 at 11:07:44AM +0200, Vlad Zolotarov wrote: >> >> On 11/26/15 22:35, Thomas Monjalon wrote: >>> When introducing LRO, Vlad has defined the macro RTE_ETHDEV_HAS_LRO_SUPPORT: >>> http://dpdk.org/browse/dpdk/commit/lib/librte_ether/rte_eth

[dpdk-dev] API feature check _HAS_

2015-11-29 Thread Gleb Natapov
On Sun, Nov 29, 2015 at 11:07:44AM +0200, Vlad Zolotarov wrote: > > > On 11/26/15 22:35, Thomas Monjalon wrote: > >When introducing LRO, Vlad has defined the macro RTE_ETHDEV_HAS_LRO_SUPPORT: > >http://dpdk.org/browse/dpdk/commit/lib/librte_ether/rte_ethdev.h?id=8eecb329 > > > >It allows to use t

[dpdk-dev] API feature check _HAS_

2015-11-29 Thread Vlad Zolotarov
On 11/26/15 22:35, Thomas Monjalon wrote: > When introducing LRO, Vlad has defined the macro RTE_ETHDEV_HAS_LRO_SUPPORT: > http://dpdk.org/browse/dpdk/commit/lib/librte_ether/rte_ethdev.h?id=8eecb329 > > It allows to use the feature without version check (before the release or > after a backport)

[dpdk-dev] API feature check _HAS_

2015-11-26 Thread Thomas Monjalon
When introducing LRO, Vlad has defined the macro RTE_ETHDEV_HAS_LRO_SUPPORT: http://dpdk.org/browse/dpdk/commit/lib/librte_ether/rte_ethdev.h?id=8eecb329 It allows to use the feature without version check (before the release or after a backport). Do you think it is useful? Should we define other m