Re: [dpdk-dev] [PATCH v4 1/7] malloc: introduce malloc is ready API

2021-10-19 Thread Dmitry Kozlyuk
2021-10-20 01:01 (UTC+0300), Dmitry Kozlyuk: > 2021-10-20 00:05 (UTC+0530), Harman Kalra: > [...] > > static unsigned > > check_hugepage_sz(unsigned flags, uint64_t hugepage_sz) > > { > > @@ -1328,6 +1330,7 @@ rte_eal_malloc_heap_init(void) > > { > > struct rte_mem_config *mcfg = rte_eal_ge

Re: [dpdk-dev] [PATCH v4 1/7] malloc: introduce malloc is ready API

2021-10-19 Thread Dmitry Kozlyuk
2021-10-20 00:05 (UTC+0530), Harman Kalra: [...] > static unsigned > check_hugepage_sz(unsigned flags, uint64_t hugepage_sz) > { > @@ -1328,6 +1330,7 @@ rte_eal_malloc_heap_init(void) > { > struct rte_mem_config *mcfg = rte_eal_get_configuration()->mem_config; > unsigned int i; > +

[dpdk-dev] [PATCH v4 1/7] malloc: introduce malloc is ready API

2021-10-19 Thread Harman Kalra
Implementing a new API get the state if DPDK memory management APIs are initialized. One of the use case of this API is while allocating an interrupt instance, if malloc APIs are ready memory for interrupt handles should be allocated via rte_malloc_* APIs else glibc malloc APIs are used. Eg. Alarm