The new packet framework in DPDK 1.7 is one candidate (set of) API's that
could be included in ODP (or ported to run on top of ODP). Inclusion in ODP
would allow platform specific implementations to offload more of the
processing to any suitable hardware. But just having a generic port to ODP
could be interesting.

DPDK also have IPv4 and IPv6 longest prefix match which are useful utility
functions.



On 13 August 2014 19:52, Aws Ismail <[email protected]> wrote:

> Thanks Ola for clarifying this.
>
> When you say: "we could copy bits and pieces of DPDK that functionally
> complement ODP and integrate them into ODP", does that imply new API's to
> handle pipelines and lookup tables from the Packet Framework? or would you
> leave that to the end user of that particular networking SoC to implement?
>
> Aws\
>
> On 08/13/2014 05:08 AM, Ola Liljedahl wrote:
>
>> The Packet Framework in DPDK 1.7 is on a higher abstraction level
>> compared to ODP and most of the functionality in earlier DPDK releases. The
>> Packet Framework provides building blocks for user-defined pipelines of
>> parse, lookup and modify operations on packets, essentially
>> application-level functionality. ODP provides a hardware abstraction of a
>> networking SoC. Two very different things.
>>
>> We don't have any DPDK compatibility today in ODP, I don't see how the
>> Packet Framework changes that.
>>
>> We could copy bits and pieces of DPDK that functionally complement ODP
>> and integrate them into ODP. This would be independent of the ODP
>> linux-dpdk implementation.
>>
>>
>>
>>
>>
>> On 7 August 2014 08:21, Venkatesh Vivekanandan <venkatesh.vivekanandan@
>> linaro.org <mailto:[email protected]>> wrote:
>>
>>
>>
>>
>>     On 6 August 2014 22:20, Aws Ismail <[email protected]
>>     <mailto:[email protected]>> wrote:
>>
>>         Thanks Venkatesh for the reply.
>>
>>         What I am really trying to confirm is whether the Linaro ODP
>>         team has any plans as part of the v1.0 release to add the
>>         extra set of API needed to cover DPDK's packet framework. Are
>>         there any plans down the pipeline to have that after LCU2014?
>>
>>
>>     When we migrate to DPDK 1.7 (which is not decided yet), we will
>>     have to support any extra API needed. As we said earlier, please
>>     feel free to contribute.
>>
>>
>>         Aws\
>>
>>         On 08/04/2014 08:56 AM, Venkatesh Vivekanandan wrote:
>>
>>
>>
>>
>>             On 4 August 2014 11:49, Venkatesh Vivekanandan
>>             <[email protected]
>>             <mailto:[email protected]>
>>             <mailto:[email protected]
>>             <mailto:[email protected]>>> wrote:
>>
>>
>>
>>
>>                 On 1 August 2014 21:07, Aws Ismail
>>             <[email protected] <mailto:[email protected]>
>>                 <mailto:[email protected]
>>             <mailto:[email protected]>>> wrote:
>>
>>                     I am wondering if there is a plan to move from
>>             DPDK 1.6r2 to
>>                     1.7 for the ODP-DPDK.
>>
>>
>>                 We are planning to do a demo at LCU14 and still we are
>>             looking at
>>                 the performance chokes with the current odp-dpdk. We
>>             will not be
>>                 moving to 1.7 until everything works fine as per the
>>             demo plan.
>>                 Probably in the end we may revisit, if moving to 1.7
>>             gives any
>>                 added value.
>>
>>
>>                     The reason I am asking is because DPDK 1.7
>>             introduces a new
>>                     set of libraries, which
>>                     are grouped under the name "Packet Framework" (See
>>             chapter 29
>>                     of the latest DPDK
>>                     user guide for more info on this).
>>
>>                     This implies ODP will need to have an extra set of
>>             API to
>>                     cover new DPDK building
>>                     blocks such as librte_pipeline, librte_port,
>>             librte_table.
>>
>>                 This will be done once we migrate to support DPDK 1.7
>>
>>
>>             We had an internal discussion on this topic and felt that
>>             it is always better to have the patch set without wasting
>>             time. We would like to have your contributions anytime,
>>             but we might be in a position to merge the changes related
>>             to DPDK 1.7 in ODP to mainstream ODP _only_ after LCU14,
>>             as we don't want to have developmental changes close to
>>             LCU14, unless it is to improve performance on existing 1.6r2.
>>
>>             As you might be aware of, ODP can be cloned from
>>             http://23.21.56.198/lng/odp.git or using
>>             gitclonegit://git.linaro.org/lng/odp.git
>>             <http://git.linaro.org/lng/odp.git>
>>             <http://git.linaro.org/lng/odp.git>
>>
>>
>>             Please go ahead, make the changes and send us the patch set.
>>
>>
>>                     Thanks.
>>
>>                     Aws\
>>
>>                     _______________________________________________
>>                     lng-odp mailing list
>>             [email protected] <mailto:[email protected]>
>>             <mailto:[email protected]
>>             <mailto:[email protected]>>
>>             http://lists.linaro.org/mailman/listinfo/lng-odp
>>
>>
>>
>>
>>
>>
>>     _______________________________________________
>>     lng-odp mailing list
>>     [email protected] <mailto:[email protected]>
>>     http://lists.linaro.org/mailman/listinfo/lng-odp
>>
>>
>>
>
_______________________________________________
lng-odp mailing list
[email protected]
http://lists.linaro.org/mailman/listinfo/lng-odp

Reply via email to