Re: [dpdk-dev] [PATCH v2] eal: promote some service core functions to stable

20/06/2019 21:02, Gage Eads: > The functions rte_service_may_be_active(), rte_service_lcore_attr_get(), > and rte_service_attr_reset_all() were introduced nearly a year ago in DPDK > 18.08. They can be considered non-experimental for the 19.08 release. > > rte_service_may_be_active() is used by th

Re: [dpdk-dev] [PATCH v2] eal: promote some service core functions to stable

On Thu, Jun 20, 2019 at 9:03 PM Gage Eads mailto:gage.e...@intel.com>> wrote: The functions rte_service_may_be_active(), rte_service_lcore_attr_get(), and rte_service_attr_reset_all() were introduced nearly a year ago in DPDK 18.08. They can be considered non-experimental for the 19.08 release. r

Re: [dpdk-dev] [PATCH v2] eal: promote some service core functions to stable

On Thu, Jun 20, 2019 at 9:03 PM Gage Eads wrote: > The functions rte_service_may_be_active(), rte_service_lcore_attr_get(), > and rte_service_attr_reset_all() were introduced nearly a year ago in DPDK > 18.08. They can be considered non-experimental for the 19.08 release. > > rte_service_may_be_a

[dpdk-dev] [PATCH v2] eal: promote some service core functions to stable

The functions rte_service_may_be_active(), rte_service_lcore_attr_get(), and rte_service_attr_reset_all() were introduced nearly a year ago in DPDK 18.08. They can be considered non-experimental for the 19.08 release. rte_service_may_be_active() is used by the sw PMD, and this commit allows it to