Hi,
Thanks. So, is the workaround for now to start the threads, and do all
the memory reservation on the thread? And to call odp_shm_reserve()
instead of simple malloc() calls? Can I use multiple buffer pools, one
for each thread or interface?
BR,
Gabor
P.s.: Do you know when will this issue in the API be fixed (e.g. in next
release or whatever)?
On 05/08/2015 09:06 AM, Jerin Jacob wrote:
On Thu, May 07, 2015 at 05:00:54PM +0100, Zoltan Kiss wrote:
Hi,
I'm not aware of any such interface, but others with more knowledge can
comment about it. The ODP-DPDK implementation creates buffer pools on the
NUMA node where the pool create function were actually called.
current ODP spec is not NUMA aware. We need to have API to support nodes
enumeration and
explicit node parameter to alloc/free resource from specific node like
odp_shm_reserve_onnode(node, ...)
and while keeping existing API odp_shm_reserve() allocated on node where the
current code runs
Regards,
Zoli
On 07/05/15 16:32, Gábor Sándor Enyedi wrote:
Hi!
I just started to test ODP, trying to write my first application, but
found a problem: if I want to write NUMA aware code, how should I
allocate memory close to a given thread? I mean, I know there is
libnuma, but should I use it? I guess not, but I cannot find memory
allocation functions in ODP. Is there a function similar to
numa_alloc_onnode()?
Thanks,
Gabor
_______________________________________________
lng-odp mailing list
lng-odp@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/lng-odp
_______________________________________________
lng-odp mailing list
lng-odp@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/lng-odp
_______________________________________________
lng-odp mailing list
lng-odp@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/lng-odp
