On Wed, Oct 22, 2014 at 06:15:37PM +0400, Maxim Uvarov wrote: > On 10/22/2014 06:02 PM, Jerin Jacob wrote: > >I think, you can create the queue in odp_pktio_open and attach it and then > >expose the queues through odp_pktio_outq_getdef. > Yes, I can go with: > odp_pktio_outq_getdef(pktio) = ipc_queue; > > In that case odp_pktio_outq_setdef is not needed. > > > > >Other point is the use of hard-cored name like "ipc_pktio" in application > >IMO its not portable. > >I think we should have API to enumerate all PKTIO in the given platform > >along with capabilities(like 10G, IPC) then application can choose the > >pktio for given capability.There can be a case of multiple IPC PKTIOs in > >a platform as well. > It's not hard coded. It's simple name provided to odp_pktio_open(), > odp_pktio_lookup(), > you can change it to any other. In example I named it ipc_pktio. You can > create as much pktios > as you can but with different names. I do not see limitation here.
I agree, its not a limitation. From ODP platform implementer perceptive, We would like avoid(if possible) any platform specific change in examples and test directory and maintain it separately. I suggest to use at least a command line argument for the pktio name or lets enumerate all the pktio in given platform and use the first pktio with IPC capability. > > Maxim. > > _______________________________________________ lng-odp mailing list lng-odp@lists.linaro.org http://lists.linaro.org/mailman/listinfo/lng-odp
