On 28 November 2014 at 12:40, Stuart Haslam <[email protected]> wrote: > On Fri, Nov 28, 2014 at 05:53:07AM +0000, Venkatesh Vivekanandan wrote: >> Hi Stuart/Petri, >> >> I couldn't find odp_pktio_<recv/send> in recent pktio design doc. Are we >> deprecating these API's? > > Yes, at least that's what I'm suggesting. > >>Are we deprecating the burst mode that is currently supported in pktio/l2fwd >>applications?. > > No, they'd be modified to use polled queues and odp_queue_deq_multi(). Queues are the generic abstraction in ODP used to send and receive buffers (e.g. packets). How those queues are implemented and the function of specific queues are implementation specific. Some queues may represent pktio input and output.
I think it is up to the ODP implementation to implement pktio using queues however it desires. E.g. when enqueueing a buffer on a queue which happens to represent pktio egress, the odp_queue_enq() implementation could perform the packet transmission directly, there does not have to be any actual queue between the application and the pktio hardware. Everyone agree with this interpretation? -- Ola > > I think odp_pktio_recv/send were never really intended to be part of the > API and they don't fit with the intended ODP push/pull execution models. > > Also direct I/O (without queues) isn't supported on many of the target > platforms, so they'd either not be able to support these APIs or would > need a software layer on top of the queue APIs. > >> >> Thanks, >> Venkatesh. > > -- > Stuart. > > > _______________________________________________ > 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
