Ubuntu
dpdk package

ubuntu/+source/dpdk:ubuntu/lunar-devel

  1. Git
  2. lp:ubuntu/+source/dpdk
  3. ubuntu/lunar-devel
Last commit made on 2023-07-27
Get this branch:
git clone -b ubuntu/lunar-devel https://git.launchpad.net/ubuntu/+source/dpdk
Members of git-ubuntu import can upload to this branch. Log in for directions.

Branch merges

Branch information

Name:
ubuntu/lunar-devel
Repository:
lp:ubuntu/+source/dpdk

Recent commits

1208d2c... by Miriam España Acebal

changelog: Merge LTS stable release 22.11.2 (LP: #2026351)

9fc9a9b... by Miriam España Acebal

 * d/not-installed, d/rules: MANA poll mode driver library is not being installed

9806219... by Miriam España Acebal

 * d/rules: avoid path length issues in build time test

280e29d... by Miriam España Acebal

  * Add new internal/experimental symbols

c6e80ca... by Miriam España Acebal

 * d/p/disable-parallel-sphinx.patch: fix reprotest for parallel sphinx

2af35c7... by Miriam España Acebal

stable release update (22.11.2)

0cb92f4... by Christian Ehrhardt 

update-maintainer

Signed-off-by: Christian Ehrhardt <email address hidden>

fd97462... by Christian Ehrhardt 

changelog: fix flaky arm64 test issues

My change is already in Debian, the next MRE might be just a sync over.
But we can not wait blocking so many things with tests randomly failing.

Signed-off-by: Christian Ehrhardt <email address hidden>

c69cad5... by Christian Ehrhardt 

d/t/test-fastsuite: test env before breaking tests for known issues

As we had it in the past with the full testsuite on x86 (missing sse4.2)
we now also have some arm64 systems only do armv8.0 without crc32 (non
mandatory feature).

That triggers issues like
  HASH: Unsupported CRC32 algorithm requested using CRC32_SW
  ERROR: This system does not support "CRC32".
  Please check that RTE_MACHINE is set correctly.
  EAL: FATAL: unsupported cpu type.
  EAL: unsupported cpu type.
  63/63 DPDK:fast-tests / telemetry_all FAIL
             1.22s (exit status 255 or signal 127 SIGinvalid)

This breaks all the tests and flags it as regression which is wrong.

Background:
config/meson.build detects that it is on arm and then processes
config/arm/meson.build which checks for __ARM_FEATURE_CRC32 (a required flag
anyway) and then stores that it considered this to be present in
RTE_COMPILE_TIME_CPUFLAGS.
Note: The machine type "default" is the least optimized most common
denominator by DPDK. And on arm that is mapped to generic. In Focal that
was "['default', ['-march=armv8-a+crc']]," in Jammy the core split arch and
features but still is:
    'generic': {
        'march': 'armv8-a',
        'march_features': ['crc'],
        'compiler_options': ['-moutline-atomics']
    },
So requiring CRC32 is not new and a minimum as defined by upstream.

Then at runtime (or test time for us) on load of the binary it checks if the
environment is having all features that it expects which is great - much better
than a late crazy crash.
So it checks for crc32 which not all our test environments seem to have.

Just as with SSE4.2 which is a simular situation on x86 we should be adding
a check to the tests to reduce flakyness of test results.

Signed-off-by: Christian Ehrhardt <email address hidden>

d858fb3... by Luca Boccassi

22.11.1-2 (patches unapplied)

Imported using git-ubuntu import.