A pool may be associated with a pktio at open time, but this association is not exclusive. In theory an ODP implementation could defer actual pool creation until it was first used, but such an approach would be unlikely to yield any real benefits while creating a lot of complications along the way since odp_pool_create() is the only opportunity the implementation has to fail the pool creation in a defined manner.
On Thu, Jun 15, 2017 at 2:29 AM, Bala Manoharan <bala.manoha...@linaro.org> wrote: > Same here. Pool is created during odp_pool_create API. > > > Regards, > Bala > > On 15 June 2017 at 12:36, Nikhil Agarwal <nikhil.agar...@nxp.com> wrote: > >> Pool is created at odp_pool_create only. You can allocate packets form it >> even before pktio_open. >> >> Regards >> Nikhil >> >> -----Original Message----- >> From: lng-odp [mailto:lng-odp-boun...@lists.linaro.org] On Behalf Of >> Honnappa Nagarahalli >> Sent: Thursday, June 15, 2017 9:27 AM >> To: lng-odp-forward <lng-odp@lists.linaro.org> >> Subject: [lng-odp] Mem pool creation in Cavium/NXP implementations >> >> Hi Bala/Nikhil, >> I was wondering when is the memory pool created in your implementation >> of ODP? The programming model is that the application creates the memory >> pool and passes that pool to the pkt I/O during packet I/O open call. Do >> you actually create the pool when the application calls odp_pool_create? Or >> is the pool created during packet I/O open? >> >> Appreciate your answers. >> >> Thank you, >> Honnappa >>
