Re: [lng-odp] v1.14.0.0 was tagged!

[Savolainen, Petri (Nokia - FI/Espoo)]

Hi,

A month has passed. I'd suggest that we tag 1.15 and include parser 
configuration API changes from api-next. Other things in api-next seems to lack 
implementation still. Crypto sha1/sha512 is the next candidate to get into 1.15.

-Petri


> -Original Message-
> From: lng-odp [mailto:lng-odp-boun...@lists.linaro.org] On Behalf Of Maxim
> Uvarov
> Sent: Wednesday, March 01, 2017 9:05 PM
> To: lng-odp@lists.linaro.org
> Subject: [lng-odp] v1.14.0.0 was tagged!
> 
> v1.14.0.0 passed all CI tests and was tagged.
> 
> Detailed changelog is available in corresponding changelog commit which
> is bellow in this email.
> 
> Thank you,
> Maxim.
> 

[lng-odp] v1.14.0.0 was tagged!

[Maxim Uvarov]

v1.14.0.0 passed all CI tests and was tagged.

Detailed changelog is available in corresponding changelog commit which
is bellow in this email.

Thank you,
Maxim.


On 02/26/17 21:04, Bill Fischofer wrote:
> Signed-off-by: Bill Fischofer 
> ---
>  CHANGELOG | 144 
> ++
>  1 file changed, 144 insertions(+)
> 
> diff --git a/CHANGELOG b/CHANGELOG
> index 72bf2253..a550a723 100644
> --- a/CHANGELOG
> +++ b/CHANGELOG
> @@ -1,3 +1,147 @@
> +== OpenDataPlane (1.14.0.0)
> +=== New Features
> + APIs
> +ODP v1.14.0.0 represents another preview of the Tiger Moth release series and
> +introduces new APIs and extensions.
> +
> += Packet References
> +Packet references are a lightweight mechanism to allow applications to create
> +and manipulate different "views" of packets. These views consist of shared
> +bytes common to all references created on the same `odp_packet_t`, possibly
> +prefixed with unique headers that are private to each reference. Five new 
> APIs
> +are introduced to enable this feature:
> +
> +`odp_packet_ref_static()`::
> +Static references allow a single packet to have multiple "aliases", all of
> +which must be treated as read only. This is useful, for example, to retain
> +a reference to a packet being transmitted to support retransmit processing,
> +since the actual storage represented by a packet is not released until all
> +references to it have been freed via `odp_packet_free()` calls.
> +
> +`odp_packet_ref()`::
> +Dynamic references differ from static references is that they permit the
> +individual `odp_packet_t` handles to have unique prefixes created via
> +`odp_packet_push_head()` or `odp_packet_extend_head()` calls. This can be
> +used, for example, to support multicasting packets to different destinations
> +by creating packets that consist of unique headers followed by a common 
> shared
> +payload.
> +
> +`odp_packet_ref_pkt()`::
> +Similar to `odp_packet_ref()`, but creates a dynamic reference by prepending 
> a
> +preexisting header onto another packet.
> +
> +`odp_packet_has_ref()`::
> +Returns a boolean indicator of whether a given `odp_packet_t` has other
> +references that share bytes with this packet.
> +
> +`odp_packet_unshared_len()`::
> +Returns the number of unshared bytes accessible through a given 
> `odp_packet_t`
> +handle. These are the only bytes that should be changed. All other bytes
> +in the packet should be treated as read only as they are shared with other
> +`odp_packet_t` handles.
> +
> +Note that while the packet reference APIs and associated validation tests are
> +present in this release, the `odp-linux` reference implementation currently
> +implements references via packet copying. A zero-copy implementation of 
> packet
> +references is planned to be part of the ODP v1.15.0.0 release.
> +
> + ABI Specification
> +ODP has supported an Application Binary Interface (ABI) that permits
> +applications to be generated that are binary portable between select ODP
> +implementations. This is now formalized with the addition of structures that
> +permit ABI specifications to be defined that are shared between ODP
> +implementations. ODP provides a default ABI specification that is the same as
> +was provided before. This change means that additional ABIs may be defined
> +that are optimized to collections of platforms that share an Instruction Set
> +Architecture (ISA) and subscribe to them.
> +
> +ABI specifications live in the `include/odp/arch/...` directory.
> +
> + Instance Query (iQuery) Scheduler
> +Adding to the range of scheduler implementations supported by `odp-linux`, a
> +new scheduler, the instance query scheduler, is available by specifying
> +`--enable-schedule-iquery` at `configure` time.
> +
> +This scheduler uses sparse bitmaps and offers scalability advantages when
> +dealing with large numbers of schedule queues. It otherwise offers 
> performance
> +comparable to the default ODP scheduler implementation.
> +
> +=== Helpers
> +Helpers have been reorganized to provide better independence from odp-linux
> +and to make them more useful with other ODP implementations. These
> +reorganizations are functionally transparent to ODP users but should
> +simplifying packaging and porting to other ODP implementations. This includes
> +adding the "umbrella" include file `odph_api.h` which can be used to include
> +all helper API definitions in an application.
> +
> +=== Classifier Improvements
> +The `odp-linux` reference implementation now supports Pattern Matching Rules
> +(PMRs) for IPv6 addresses, inner and outer VLAN IDs, and inner and outer
> +Ethernet types.
> +
> +=== Performance
> +
> + Improved inlining for embedded applications
> +The `odp-linux` reference implementation now offers improved inlining support
> +for ODP APIs for applications compiled against ODP configured with the
> +`--enable-abi-compat=no` option, meaning they wish to