On Mon, 3 Nov 2014 12:11:26 -0600 Bill Fischofer <[email protected]> wrote: > ODP APIs are designed to be used *a la carte* by applications, as ODP is a > framework, not a platform. So feel free to mix malloc() or your own memory > management or other API calls in as needed. > > What ODP requires is the types specified in its APIs, so for example the > only way to get an odp_buffer_t is via the odp_buffer_alloc() call. > odp_buffer_alloc() in turn requires an odp_buffer_pool_t and that in turn > requires an odp_buffer_pool_create() call. > > ODP_BUFFER_TYPE_RAW simply exposes the basic block manager functions of the > ODP buffer APIs. Again, you're free to use them for whatever purpose the > application wants. Obviously one reason for doing so is to gain > portability across potentially different memory management implementations.
Thanks Bill. This leads me to few additional questions: Are all memory-related ODP APIs mandatory (must be implemented by the platform)? Are they required to provide any other benefit over standard (or custom) allocation routines besides the portability guarantee? Regards, Shmulik _______________________________________________ lng-odp mailing list [email protected] http://lists.linaro.org/mailman/listinfo/lng-odp
