Hi Petri, generic extracts would be packet areas given by offset and length. For example I'm able with the frame distribution engine on DPAA1 platforms to encode the frame queue directly in the frame , e.g. in the last 3 bytes of the source MAC address (this is only an example , arbitrary packet bytes can be used). This would be a direct queue selection feature (queue id is computed and not searched in a typical lookup table) , complementary to distribution and not involving classification.
Hope this helps, Alex On 31 March 2015 at 11:56, Savolainen, Petri (Nokia - FI/Espoo) < petri.savolai...@nokia.com> wrote: > Hi Alex, > > > > Could you explain a bit more what you mean with extracts here. Detailed > classification (packet field + mask/range => queue / set of queues) would > be still handled with classification API. This API would offer an easy way > to spread typical flows (e.g. 5-tuple) into multiple queues (same queue > type, priority, sync, group). > > > > -Petri > > > > > > *From:* ext Alexandru Badicioiu [mailto:alexandru.badici...@linaro.org] > *Sent:* Tuesday, March 31, 2015 11:37 AM > *To:* Savolainen, Petri (Nokia - FI/Espoo) > *Cc:* LNG ODP Mailman List > *Subject:* Re: [lng-odp] [RFC 5/8] api: packet_io: added packet input > queue API definitions > > > > Hi Petri, > > I think it would be useful (for hardware which supports) to be able to > specify generic packet extracts in addition to protocol related fields. > While hash works well for uniform distribution, having generic extracts > from the packet helps in directly selecting the input queue. > > > > Thanks, > > Alex >
_______________________________________________ lng-odp mailing list lng-odp@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lng-odp
