Hi, I have a slightly different understanding of pull vs push scheduler working modes. Pull is when cores trigger the start the HW scheduler (they pull frames from the scheduler), push is when the HW scheduler runs independently and the cores just collect the frames (the scheduler pushes the frames to the cores). odp_schedule() call looks like pull but really there is no restriction for the implementation to keep the HW scheduler idle between odp_schedule invocations. I suppose if some platforms has HW queues then there's no need to support software poll queues, what is done by application SW in this case is the decision when to serve each queue. Most ODP packet apps to date use odp_schedule() so IMO this should be supported in SW if the platform doesn't have a HW scheduler block.
Alex On 1 December 2014 at 13:36, Jacob, Jerin <[email protected]> wrote: > > I would like to understand the ODP _application_ expectation with ODP > pull(odp_schedule()) and push(polled queues) execution model. > > Is it expected that a confirming ODP platform implementation need to > support both models ? > or at least one model shall be supported by confirming ODP platform > implementation ? > > In Cavium perspective, We have two different category of SoCs in which we > are trying to implement ODP. > 1) Networking SoC with hardware accelerated odp_schedule() support. > 2) Enterprise server(ARMV8) SoC with Network Function virtualization > support and NFV capabilities are > inline with state of art enterprise SoC like Intel(DPDK) per socket. > > So in this context, My queries are > 1)Does it make sense to support(emulate in software) polled queues in > former category of SoC ? if yes what is the use case ? > 2)An confirming ODP implementation needs to emulate odp_shedule() in > software if HW supports is not available ? > Is it worth to emulate ? or application to use the push execution > model(polled queues) like DPDK ? > > Any thoughts ? > > - Jerin​ > > > _______________________________________________ > lng-odp mailing list > [email protected] > http://lists.linaro.org/mailman/listinfo/lng-odp >
_______________________________________________ lng-odp mailing list [email protected] http://lists.linaro.org/mailman/listinfo/lng-odp
