Parsing is logically a function of classification, not pktio, so any configuration should be expressed in those terms. This is one of the areas of performance tuning we need to look at for OVS.
Parsing is free for those platforms that have HW classification engines. It's only an issue for SW classifiers, so you don't want to be too heavy-handed here. Ideally what we want is for OVS to stop classifying and instead rely on the underlying classification it gets from ODP so it can take transparent advantage of HW classification support when available. On Wed, Apr 8, 2015 at 12:07 PM, Maxim Uvarov <[email protected]> wrote: > On 04/08/15 20:02, Zoltan Kiss wrote: > >> Hi, >> >> OVS has a major performance issue with pktio at the moment: pktio always >> does parsing, but OVS does it for itself as well, and it is quite deeply >> woven into its code, so we can't easily modify it to use the ODP parsed >> data. Also, not every platform accelerate that (e.g. DPDK), at the moment >> it would make more sense to make parsing optional for pktio, so an >> application can opt not to do it. >> I can see two options now to define the API: >> - odp_pktio_open get a new bool parameter for this purpose >> - we create a new odp_pktio_enable/disable_parse function pair for this >> purpose >> >> Any opinions about these options? >> >> Regards, >> >> Zoli >> > > Hi Zoltan, do you have numbers with parsing and without? > > Maxim. > > _______________________________________________ >> lng-odp mailing list >> [email protected] >> https://lists.linaro.org/mailman/listinfo/lng-odp >> > > _______________________________________________ > lng-odp mailing list > [email protected] > https://lists.linaro.org/mailman/listinfo/lng-odp >
_______________________________________________ lng-odp mailing list [email protected] https://lists.linaro.org/mailman/listinfo/lng-odp
