Hi,

As demonstrated by odp/examples, libc memory allocation routines (malloc
and friends) aren't been used by ODP apps (unless for a very tight
temporary scope, usually in the control thread).

Application's data structures are allocated either using odp_buffer_pool
interface (e.g. odp_ipsec.c allocating its private per packet context
structure using a ODP_BUFFER_TYPE_RAW pool), or directly using 
odp_shm_reserve and managing it internally (e.g. odp_ipsec_fwd_db.c,
odp_ipsec_sp_db.c etc).

Questions:

Must the application use ODP memory allocation interfaces at all times?
Or only for data structures accessed at data-path routines?
Or only when allocating them from within data-path routines?

Any preference for when to use a ODP_BUFFER_TYPE_RAW pool vs. allocating
a shared memory and managing data structures internally?

Thanks,
Shmulik

_______________________________________________
lng-odp mailing list
lng-odp@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/lng-odp

Reply via email to