git-lng-odp

git-lng-odp@lists.linaro.org

1 participants
1207 discussions

[COMMIT] branch master updated. v1.10.1.0-83-g8e9c4fe

by git＠git-us.linaro.org

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "". The branch, master has been updated via 8e9c4fe4ec0611ddde0b027d7c45a1b92d182a0e (commit) from 5d4f6cbd12a7f079917bc5ad18b710b3e34485b1 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 8e9c4fe4ec0611ddde0b027d7c45a1b92d182a0e Author: Bill Fischofer <bill.fischofer(a)linaro.org> Date: Tue Aug 9 18:56:42 2016 -0500 doc: release-guide: elaborate release naming scheme Add additional detail and examples to the description of the release naming scheme used by ODP, detailing the expected impact to ODP applications and/or other ODP implementations for each change. Signed-off-by: Bill Fischofer <bill.fischofer(a)linaro.org> Reviewed-by: Petri Savolainen <petri.savolainen(a)nokia.com> Signed-off-by: Maxim Uvarov <maxim.uvarov(a)linaro.org> diff --git a/doc/process-guide/release-guide.adoc b/doc/process-guide/release-guide.adoc index 8816c03..788eb6b 100644 --- a/doc/process-guide/release-guide.adoc +++ b/doc/process-guide/release-guide.adoc @@ -116,28 +116,82 @@ atomically as possible * the maintainer tags the master branch == Releases == -All releases are from master. - -They are tagged in the repository using the format -v<Generation>.<Major>.<Minor>.<Impl> -There are three release types with differing frequencies and impact to the -applications. +All releases are from a tag in the master branch of the ODP git +repository. Recall that ODP consists of three separate components: + +* An API Specification +* Multiple independently owned and maintained _implementations_ of the ODP API +* A Validation Test Suite that tests implementation conformance to the ODP API + +Included with the main ODP git repository is the `odp-linux` reference +implementation of the ODP API, and it also has an associated service stream +that is independent of all other ODP implementations. This means that the ODP +release naming conventions address the needs of all three of these components, +which is accomplished via a multi-level structure using the format: + +*v<Generation>.<Major>.<Minor>.<Point>* + +This is used as the tag from which all ODP releases are published and is also +used as the release identifier in the CHANGELOG for each release. The first +three of these digits represent the ODP API level, and these reflect three +types of API changes with differing frequencies and impact to applications and +other ODP implementations. A fourth digit is used to reflect changes to other +items included within the ODP git repository. In addition, each individual ODP +implementation will have its own service stream identifier that is defined +using whatever conventions meet its needs. === Generation releases === A generation release indicates a major completion of work, and a possible -change in direction for the API. Same as for Major release plus they are -defined by the Steering committee. +change in direction for the API. Generation release changes are approved by the +LNG Steering Committee, which is the governing body for ODP. === Major releases === -Major (API) releases are scheduled to be about once a -quarter, but when there is significant progress made they may be more frequent. +Major (API) releases are used when new APIs or capabilities are introduced or +changes are made to existing APIs that are not backwards-compatible. Major +release changes thus potentially affect ODP applications as well as +implementations. + +=== Minor releases === +Minor (API) releases are used when new APIs or capabilities are introduced or +changes are made to existing APIs in a backwards-compatible manner. Examples +of these might be wording changes in API documentation, or introducing new +APIs that are orthogonal to the existing set of APIs and hence have no impact +on existing applications that do not make use of them. Minor release changes +should therefore have no impact on existing ODP applications but will have +impact for ODP implementations that need to support these API additions and +changes. + +NOTE: The first three digits of the release name are the API version returned +by the `odp_version_api_str()` API. === Point releases === -General bug fixes and other non API altering changes are gathered and a release -made every month if sufficient change has accumulated. - -=== Implementation (Impl) === -Platform specific free form text relating to the version. +General bug fixes and other non API altering changes are gathered and a +release made every month if sufficient change has accumulated. Examples of a +point release would be additional documentation, extensions or corrections to +the validation test suite, additions or corrections to helpers, example +programs, etc. No API changes are permitted in a point release, so ODP +applications are not impacted. Other ODP implementations _may_ be impacted +if, for example, a bug is fixed in a validation test that results in a latent +bug in other implementations being exposed. + +=== Implementation Service Strings === +Beyond the four-digit release name, platform specific free form text is used +to capture the service level of each ODP implementation. This field is for the +sole use of implementations to represent their individual service streams. Its +format may vary between implementations. For example, the `odp-linux` +reference implementation uses a simple incrementing digit (0, 1, 2, +etc.). Other implementations may use `Build xxxx` or something similar. +Changes in this designator have no impact on and may be ignored by other ODP +implementations. The only changes that ODP applications should see is +corrected functional or performance behavior when running on that specific ODP +implementation. + +NOTE: The full four-digit release name plus implementation service string as +well as other platform-specific identification information is returned by the +`odp_version_impl_str()` API. This may be useful, for example, in logging an +error to include in a bug report to the vendor that owns and supports this ODP +implementation. The release-independent name of a given implementation (for +identification purposed) is supplied by the `odp_version_impl_name()` API. == Deprecating part of the API Deleting or changing the published API follows the normal <<anchor-1,process>>, with the following additional rules: ----------------------------------------------------------------------- Summary of changes: doc/process-guide/release-guide.adoc | 84 +++++++++++++++++++++++++++++------- 1 file changed, 69 insertions(+), 15 deletions(-) hooks/post-receive --

9 years, 7 months

[COMMIT] branch master updated. v1.10.1.0-82-g5d4f6cb

by git＠git-us.linaro.org

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "". The branch, master has been updated via 5d4f6cbd12a7f079917bc5ad18b710b3e34485b1 (commit) from 26b90314427f088c7f7e2accd41ec7db5d396265 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 5d4f6cbd12a7f079917bc5ad18b710b3e34485b1 Author: Mike Holmes <mike.holmes(a)linaro.org> Date: Thu Aug 4 09:18:14 2016 -0400 test:linux-generic: run odp_scheduling in process mode Set up the environment to allow calling the performance tests in process mode as part of make check when enabled. To run the tests use --enable-test-perf-proc Initial patch using odp_scheduling as a proof Signed-off-by: Mike Holmes <mike.holmes(a)linaro.org> Reviewed-by: Brian Brooks <brian.brooks(a)linaro.org> Signed-off-by: Maxim Uvarov <maxim.uvarov(a)linaro.org> diff --git a/configure.ac b/configure.ac index c0f0f21..6551287 100644 --- a/configure.ac +++ b/configure.ac @@ -169,6 +169,7 @@ AM_CONDITIONAL([test_installdir], [test "$testdir" != ""]) AM_CONDITIONAL([cunit_support], [test x$cunit_support = xyes ]) AM_CONDITIONAL([test_vald], [test x$test_vald = xyes ]) AM_CONDITIONAL([test_perf], [test x$test_perf = xyes ]) +AM_CONDITIONAL([test_perf_proc], [test x$test_perf_proc = xyes ]) AM_CONDITIONAL([test_cpp], [test x$test_cpp = xyes ]) AM_CONDITIONAL([test_helper], [test x$test_helper = xyes ]) AM_CONDITIONAL([test_example], [test x$test_example = xyes ]) @@ -302,6 +303,7 @@ AC_MSG_RESULT([ cunit: ${cunit_support} test_vald: ${test_vald} test_perf: ${test_perf} + test_perf_proc: ${test_perf_proc} test_cpp: ${test_cpp} test_helper: ${test_helper} test_example: ${test_example} diff --git a/test/linux-generic/Makefile.am b/test/linux-generic/Makefile.am index f5cc52d..4660cf0 100644 --- a/test/linux-generic/Makefile.am +++ b/test/linux-generic/Makefile.am @@ -3,7 +3,7 @@ TESTS_ENVIRONMENT += TEST_DIR=${top_builddir}/test/common_plat/validation ALL_API_VALIDATION_DIR = ${top_builddir}/test/common_plat/validation/api -SUBDIRS = +SUBDIRS = performance if test_vald TESTS = validation/api/pktio/pktio_run.sh \ diff --git a/test/linux-generic/m4/configure.m4 b/test/linux-generic/m4/configure.m4 index 9eec545..6b92201 100644 --- a/test/linux-generic/m4/configure.m4 +++ b/test/linux-generic/m4/configure.m4 @@ -1,5 +1,8 @@ +m4_include([test/linux-generic/m4/performance.m4]) + AC_CONFIG_FILES([test/linux-generic/Makefile test/linux-generic/validation/api/shmem/Makefile test/linux-generic/validation/api/pktio/Makefile test/linux-generic/pktio_ipc/Makefile - test/linux-generic/ring/Makefile]) + test/linux-generic/ring/Makefile + test/linux-generic/performance/Makefile]) diff --git a/test/linux-generic/m4/performance.m4 b/test/linux-generic/m4/performance.m4 new file mode 100644 index 0000000..7f54b96 --- /dev/null +++ b/test/linux-generic/m4/performance.m4 @@ -0,0 +1,9 @@ +########################################################################## +# Enable/disable test-perf-proc +########################################################################## +test_perf_proc=no +AC_ARG_ENABLE([test-perf-proc], + [ --enable-test-perf-proc run test in test/performance in process mode], + [if test "x$enableval" = "xyes"; then + test_perf_proc=yes + fi]) diff --git a/test/linux-generic/performance/.gitignore b/test/linux-generic/performance/.gitignore new file mode 100644 index 0000000..7e563b8 --- /dev/null +++ b/test/linux-generic/performance/.gitignore @@ -0,0 +1,2 @@ +*.log +*.trs diff --git a/test/linux-generic/performance/Makefile.am b/test/linux-generic/performance/Makefile.am new file mode 100644 index 0000000..cb72fce --- /dev/null +++ b/test/linux-generic/performance/Makefile.am @@ -0,0 +1,13 @@ +include $(top_srcdir)/test/Makefile.inc + +TESTS_ENVIRONMENT += TEST_DIR=${builddir} + +TESTSCRIPTS = odp_scheduling_run_proc.sh + +TEST_EXTENSIONS = .sh + +if test_perf_proc +TESTS = $(TESTSCRIPTS) +endif + +EXTRA_DIST = $(TESTSCRIPTS) diff --git a/test/linux-generic/performance/odp_scheduling_run_proc.sh b/test/linux-generic/performance/odp_scheduling_run_proc.sh new file mode 100755 index 0000000..b3ef26f --- /dev/null +++ b/test/linux-generic/performance/odp_scheduling_run_proc.sh @@ -0,0 +1,26 @@ +#!/bin/sh +# +# Copyright (c) 2016, Linaro Limited +# All rights reserved. +# +# SPDX-License-Identifier: BSD-3-Clause +# +# Script that passes command line arguments to odp_scheduling test when +# launched by 'make check' + +TEST_DIR="${TEST_DIR:-$(dirname $0)}" +PERFORMANCE="$TEST_DIR/../../common_plat/performance" +ret=0 + +run() +{ + echo odp_scheduling_run_proc starts with $1 worker threads + echo ===================================================== + + $PERFORMANCE/odp_scheduling${EXEEXT} --odph_proc -c $1 || ret=1 +} + +run 1 +run 8 + +exit $ret ----------------------------------------------------------------------- Summary of changes: configure.ac | 2 ++ test/linux-generic/Makefile.am | 2 +- test/linux-generic/m4/configure.m4 | 5 ++++- .../m4/performance.m4 | 10 ++++----- .../api => linux-generic/performance}/.gitignore | 0 test/linux-generic/performance/Makefile.am | 13 +++++++++++ .../performance/odp_scheduling_run_proc.sh | 26 ++++++++++++++++++++++ 7 files changed, 51 insertions(+), 7 deletions(-) copy test/{common_plat => linux-generic}/m4/performance.m4 (51%) copy test/{common_plat/validation/api => linux-generic/performance}/.gitignore (100%) create mode 100644 test/linux-generic/performance/Makefile.am create mode 100755 test/linux-generic/performance/odp_scheduling_run_proc.sh hooks/post-receive --

9 years, 7 months

[COMMIT] branch master updated. v1.10.1.0-81-g26b9031

by git＠git-us.linaro.org

9 years, 7 months

[COMMIT] branch api-next updated. v1.10.1.0-131-g179074e

by git＠git-us.linaro.org

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "". The branch, api-next has been updated via 179074e0d0771c82d064e29a20531b75d17289d7 (commit) from 32e95a4ed19e5cd567d02125c4b74bb6e41ee197 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 179074e0d0771c82d064e29a20531b75d17289d7 Author: Bill Fischofer <bill.fischofer(a)linaro.org> Date: Tue Jul 12 21:27:05 2016 -0500 api: byteorder: avoid bitfield order doxygen omissions Resolve Bug https://bugs.linaro.org/show_bug.cgi?id=2402 by assigning explicit values to ODP_LITTLE_ENDIAN_BITFIELD and ODP_BIT_ENDIAN_BITFIELD to avoid Doxygen warnings. This makes these consistent with the usage for ODP_BIG_ENDIAN and ODP_LITTLE_ENDIAN. Also define the summary variable ODP_BITFIELD_ORDER which can be used similar to ODP_BYTE_ORDER for an explicit test of bitfield endianness. Note that this requires tests of these fields to change from #ifdef to #if. Signed-off-by: Bill Fischofer <bill.fischofer(a)linaro.org> Reviewed-by: Petri Savolainen <petri.savolainen(a)nokia.com> Signed-off-by: Maxim Uvarov <maxim.uvarov(a)linaro.org> diff --git a/helper/include/odp/helper/tcp.h b/helper/include/odp/helper/tcp.h index cabef90..fd234e5 100644 --- a/helper/include/odp/helper/tcp.h +++ b/helper/include/odp/helper/tcp.h @@ -34,7 +34,7 @@ typedef struct ODP_PACKED { odp_u32be_t ack_no; /**< Acknowledgment number */ union { odp_u16be_t doffset_flags; -#if defined(ODP_BIG_ENDIAN_BITFIELD) +#if ODP_BIG_ENDIAN_BITFIELD struct { odp_u16be_t rsvd1:8; odp_u16be_t flags:8; /**< TCP flags as a byte */ @@ -51,7 +51,7 @@ typedef struct ODP_PACKED { odp_u16be_t syn:1; odp_u16be_t fin:1; }; -#elif defined(ODP_LITTLE_ENDIAN_BITFIELD) +#elif ODP_LITTLE_ENDIAN_BITFIELD struct { odp_u16be_t flags:8; odp_u16be_t rsvd1:8; /**< TCP flags as a byte */ diff --git a/include/odp/api/spec/byteorder.h b/include/odp/api/spec/byteorder.h index 6b18eb3..38c0bdb 100644 --- a/include/odp/api/spec/byteorder.h +++ b/include/odp/api/spec/byteorder.h @@ -38,6 +38,9 @@ extern "C" { * * @def ODP_BYTE_ORDER * Selected byte order + * + * @def ODP_BITFIELD_ORDER + * Selected bitfield order */ /** diff --git a/platform/linux-generic/include/odp/api/plat/byteorder_types.h b/platform/linux-generic/include/odp/api/plat/byteorder_types.h index d4bf3d6..20d52bf 100644 --- a/platform/linux-generic/include/odp/api/plat/byteorder_types.h +++ b/platform/linux-generic/include/odp/api/plat/byteorder_types.h @@ -49,12 +49,16 @@ extern "C" { #define ODP_LITTLE_ENDIAN 1 #define ODP_BIG_ENDIAN 0 #define ODP_BYTE_ORDER ODP_LITTLE_ENDIAN - #define ODP_LITTLE_ENDIAN_BITFIELD + #define ODP_LITTLE_ENDIAN_BITFIELD 1 + #define ODP_BIG_ENDIAN_BITFIELD 0 + #define ODP_BITFIELD_ORDER ODP_LITTLE_ENDIAN_BITFIELD #else #define ODP_LITTLE_ENDIAN 0 #define ODP_BIG_ENDIAN 1 #define ODP_BYTE_ORDER ODP_BIG_ENDIAN - #define ODP_BIG_ENDIAN_BITFIELD + #define ODP_LITTLE_ENDIAN_BITFIELD 0 + #define ODP_BIG_ENDIAN_BITFIELD 1 + #define ODP_BITFIELD_ORDER ODP_BIG_ENDIAN_BITFIELD #endif typedef uint16_t __odp_bitwise odp_u16le_t; diff --git a/platform/linux-generic/include/protocols/tcp.h b/platform/linux-generic/include/protocols/tcp.h index 4e92e4b..114262e 100644 --- a/platform/linux-generic/include/protocols/tcp.h +++ b/platform/linux-generic/include/protocols/tcp.h @@ -34,7 +34,7 @@ typedef struct ODP_PACKED { odp_u32be_t ack_no; /**< Acknowledgment number */ union { odp_u16be_t doffset_flags; -#if defined(ODP_BIG_ENDIAN_BITFIELD) +#if ODP_BIG_ENDIAN_BITFIELD struct { odp_u16be_t rsvd1:8; odp_u16be_t flags:8; /**< TCP flags as a byte */ @@ -51,7 +51,7 @@ typedef struct ODP_PACKED { odp_u16be_t syn:1; odp_u16be_t fin:1; }; -#elif defined(ODP_LITTLE_ENDIAN_BITFIELD) +#elif ODP_LITTLE_ENDIAN_BITFIELD struct { odp_u16be_t flags:8; odp_u16be_t rsvd1:8; /**< TCP flags as a byte */ ----------------------------------------------------------------------- Summary of changes: helper/include/odp/helper/tcp.h | 4 ++-- include/odp/api/spec/byteorder.h | 3 +++ platform/linux-generic/include/odp/api/plat/byteorder_types.h | 8 ++++++-- platform/linux-generic/include/protocols/tcp.h | 4 ++-- 4 files changed, 13 insertions(+), 6 deletions(-) hooks/post-receive --

9 years, 7 months

[COMMIT] branch api-next updated. v1.10.1.0-130-g32e95a4

by git＠git-us.linaro.org

9 years, 7 months

[COMMIT] branch master updated. v1.10.1.0-80-ge072ea0

by git＠git-us.linaro.org

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "". The branch, master has been updated via e072ea084a27df729d1b94c0bec2d45fb1e4d26f (commit) from 3eb700768b6369e674e5d5a9758eb39f8fd34c3d (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit e072ea084a27df729d1b94c0bec2d45fb1e4d26f Author: Mike Holmes <mike.holmes(a)linaro.org> Date: Fri Aug 5 11:37:11 2016 -0400 doc: implimenters: fix spelling Signed-off-by: Mike Holmes <mike.holmes(a)linaro.org> Reviewed-by: Bill Fischofer <bill.fischofer(a)linaro.org> Signed-off-by: Maxim Uvarov <maxim.uvarov(a)linaro.org> diff --git a/doc/implementers-guide/implementers-guide.adoc b/doc/implementers-guide/implementers-guide.adoc index 5c0e864..0e2edc0 100644 --- a/doc/implementers-guide/implementers-guide.adoc +++ b/doc/implementers-guide/implementers-guide.adoc @@ -29,7 +29,7 @@ mapping of the ODP APIs to a specific target platform. This is the focus of this document. - A Validation Test Suite. This is an independent set of routines that when -run against an ODP implmenetation verifies that it correctly implements all of +run against an ODP implementation verifies that it correctly implements all of the defined ODP APIs at a functional level. The test suite is used by implementers to self-certify their ODP implementation as well as by third-parties to verify an implementation's claim to be ODP API compliant. @@ -39,18 +39,18 @@ fully defined in the _ODP User's Guide_ === Organization of this Document This document is designed to serve two purposes. Its larger purpose is to -provide guidenace and practical advice for those wishing to implement ODP on +provide guidance and practical advice for those wishing to implement ODP on their platform. To help with this, as well as to provide deeper insight into how to think about ODP from an implementer's standpoint, this document also discusses in some depth the design and organization of a specific ODP implementation: the odp-linux reference implementation distributed as part of the main ODP git repository. By grounding theory in practice and discussing a particular example implementation, it is hoped this will provide insight into -the tradeoffs implementers should consider in approaching how to best implement +the trade-offs implementers should consider in approaching how to best implement ODP on their platforms. The section <<include_structure>> discusses the layout of the ODP include tree -from an implementer's perspective. Although implementers have wide lattitude +from an implementer's perspective. Although implementers have wide latitude in how they organize their ODP implementations, it is recommended that this layout be be observed by other implementations. Doing so both simplifies code sharing with the odp-linux reference implementation and also ensure ease of @@ -637,7 +637,7 @@ It is recommended that however a platform wishes to represent ODP abstract types, that it do so in a strongly typed manner. Using strong types means that an application that tries to pass a variable of type `odp_packet_t` to an API that expects an argument of type `odp_queue_t`, for example, will result -in a compililation error rather than some difficult to debug runtime failure. +in a compilation error rather than some difficult to debug runtime failure. The *odp-linux* reference implementation defines all ODP abstract types strongly using a set of utility macros contained in @@ -653,13 +653,13 @@ implementations choose typdefs and representations that permit the implementation to realize ODP APIs efficiently. This typically means that the handles defined by typedefs are either a pointer to an implementation-defined struct or else an index into an implementation-defined resource table. The two -LNG-provided ODP reference implemnetations illustrate both of these approaches. +LNG-provided ODP reference implementations illustrate both of these approaches. The *odp-dpdk* implementation follows the former approach (pointers) as this offers the highest performance. For example, in *odp-dpdk* an `odp_packet_t` is a pointer to an `rte_mbuf` struct, which is how DPDK represents packets. The *odp-linux* implementation, by contrast, uses indices as this permits more robust validation support while still being highly -efficient. In general, software-based implemnetations will typically favor +efficient. In general, software-based implementations will typically favor pointers while hardware-based implementations will typically favor indices. === ABI Considerations @@ -670,13 +670,13 @@ portability guarantees provided by APIs to permit binary portability as well. It is important to note that ODP neither defines nor prohibits the specification of ABIs. This is because ODP itself is an _Abstract API Specification_. As -noted earlier, abstract APIs cannot be compiled in the absense of completion +noted earlier, abstract APIs cannot be compiled in the absence of completion by an implementation that instantiates them, so the question of ABIs is really a question of representation agreement between multiple ODP implementations. If two or more ODP implementations agree on things like typedefs, endianness, alignments, etc., then they are defining an ABI which -would permit ODP applications compiled to that common set of instantations -to interoperate at a binary as well as source level. +would permit ODP applications compiled to that common set of instantiations +to inter operate at a binary as well as source level. ==== Traditional ABI ABIs can be defined at two levels. The simplest ABI is within a specific @@ -692,7 +692,7 @@ of typedefs, etc. so that the resulting output from compilation is directly executable on any platform that subscribes to that ABI. Adding a new platform in this approach simply requires that platform to accept the existing ABI specification. Note that since the output of compilation in a traditional ABI -is a ISA-specific binary that applications cannot offer binary compability +is a ISA-specific binary that applications cannot offer binary compatibility across platforms that use different ISAs. ==== Bitcode based ABI @@ -716,9 +716,9 @@ library system selects the appropriate managed binary for that target platform and loads and runs it. Adding a new platform in this approach involves adding the definition for that -platform to the libary system so that a managed binary for it can be created +platform to the library system so that a managed binary for it can be created and deployed as needed. This occurs without developer involvement since the -bitcode format that is input to this backend process is indepentent of the +bitcode format that is input to this backend process is independent of the specific target platform. Note also that since bitcode is not tied to any ISA, applications using bitcode ABIs are binary portable between platforms that use different ISAs. This occurs without loss of efficiency because the process of ----------------------------------------------------------------------- Summary of changes: doc/implementers-guide/implementers-guide.adoc | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) hooks/post-receive --

9 years, 7 months

[COMMIT] branch master updated. v1.10.1.0-79-g3eb7007

by git＠git-us.linaro.org

9 years, 7 months

[COMMIT] branch master updated. v1.10.1.0-78-gc05c1c6

by git＠git-us.linaro.org

9 years, 7 months

[COMMIT] branch api-next updated. v1.10.1.0-129-gb999565

by git＠git-us.linaro.org

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "". The branch, api-next has been updated via b9995659aabf9a20cae2ae6905b84c94b733636c (commit) via ca927a72b1f9ea2a583e8a628790d62eb93d430f (commit) via c70e9679f2827bcf9fe520ce2d1d39ca25d42c73 (commit) via abb1be33068b60290a252ce10a494338e80848e3 (commit) via b007f9d72b085005ba7b19355885c7f0096899e2 (commit) via b6a5e7039cc23e4547b11b78a12ba7f9efe6ae93 (commit) via 4c759ad5c0a4d1ece38b5cd93c24faddee9d5292 (commit) via 014a7fab6a34aacb061e53cc0b14d12aa119b03a (commit) via 48272fd98f3882a708a7302cd4e28308d59f96e9 (commit) via e63a6cc10819fccbc55ec55d4585e0619463320b (commit) from 65ea1213c75e323c4ff8ee2de48ce6dd84b1f7f2 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit b9995659aabf9a20cae2ae6905b84c94b733636c Merge: 65ea121 ca927a7 Author: Maxim Uvarov <maxim.uvarov(a)linaro.org> Date: Wed Aug 3 18:11:56 2016 +0300 Merge branch 'master' into api-next ----------------------------------------------------------------------- Summary of changes: example/ipsec/odp_ipsec_stream.h | 4 --- example/traffic_mgmt/odp_traffic_mgmt.c | 4 --- helper/chksum.c | 51 +++++++++++++++------------ include/odp/api/spec/crypto.h | 12 ++++--- platform/linux-generic/pktio/ipc.c | 37 +++++++++---------- test/linux-generic/pktio_ipc/ipc_common.c | 15 +++++--- test/linux-generic/pktio_ipc/ipc_common.h | 5 +-- test/linux-generic/pktio_ipc/pktio_ipc1.c | 45 ++++++++++++++--------- test/linux-generic/pktio_ipc/pktio_ipc2.c | 33 ++++++++++++----- test/linux-generic/pktio_ipc/pktio_ipc_run.sh | 1 + 10 files changed, 124 insertions(+), 83 deletions(-) hooks/post-receive --

9 years, 7 months

[COMMIT] branch next updated. v1.10.1.0-77-gca927a7

by git＠git-us.linaro.org

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "". The branch, next has been updated via ca927a72b1f9ea2a583e8a628790d62eb93d430f (commit) via c70e9679f2827bcf9fe520ce2d1d39ca25d42c73 (commit) via abb1be33068b60290a252ce10a494338e80848e3 (commit) via b007f9d72b085005ba7b19355885c7f0096899e2 (commit) via b6a5e7039cc23e4547b11b78a12ba7f9efe6ae93 (commit) via 4c759ad5c0a4d1ece38b5cd93c24faddee9d5292 (commit) from 014a7fab6a34aacb061e53cc0b14d12aa119b03a (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- ----------------------------------------------------------------------- Summary of changes: example/ipsec/odp_ipsec_stream.h | 4 --- example/traffic_mgmt/odp_traffic_mgmt.c | 4 --- helper/chksum.c | 51 +++++++++++++++------------ include/odp/api/spec/crypto.h | 12 ++++--- platform/linux-generic/pktio/ipc.c | 37 +++++++++---------- test/linux-generic/pktio_ipc/ipc_common.c | 15 +++++--- test/linux-generic/pktio_ipc/ipc_common.h | 5 +-- test/linux-generic/pktio_ipc/pktio_ipc1.c | 45 ++++++++++++++--------- test/linux-generic/pktio_ipc/pktio_ipc2.c | 33 ++++++++++++----- test/linux-generic/pktio_ipc/pktio_ipc_run.sh | 1 + 10 files changed, 124 insertions(+), 83 deletions(-) hooks/post-receive --

9 years, 7 months

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

git-lng-odp