Skip to content

Conversation

@PlagueCZ
Copy link
Contributor

Providing necessary changes to build against DPDK 24.

This update introduced two problems at first:

  • virtual services unable to create isolation rules
  • slow port startup (up to 1s per port)

Both of them can be fixed by removing newly introduced validation code. This is part of this PR.

While no changes to virtual service isolation is then needed, I still created PR #671 based on this one to simplify them and remove the problem altogether regardless of the DPDK patch.

Aside from this, only small changes to the codebase were required.

Fixes #668

&& patch -p1 < ../hack/dpdk_24_11_fdb_def_rule.patch \
&& patch -p1 < ../hack/dpdk_24_11_log.patch \
&& patch -p1 < ../hack/dpdk_24_11_telemetry_key.patch \
&& patch -p1 < ../hack/dpdk_24_11_no_pattern_template_validation.patch \
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought that we agreed to make this optional with a docker parameter ? or do I miss smt here ?

Copy link
Contributor Author

@PlagueCZ PlagueCZ Apr 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That was when the change would mean changing functionality. I later discovered that we can simply not validate without changing any functionality. Validation was only a feature introduced in 24, so this was never used before.

The build argument was meant to be there because the previous solution of mine would prevent anyone from using sync-flow-api, but the current solution does not prevent anything.

We can still make it a parameter of course, it's just that this is basically similar to the MTU patch now, removing some additional behavior that has been added in 24 but we do not actually need.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for clarifying. If the sync-flow-api is not effected then this can stay without Docker parameter.

@guvenc guvenc marked this pull request as ready for review May 5, 2025 16:39
@guvenc guvenc requested a review from a team as a code owner May 5, 2025 16:39
@guvenc guvenc moved this to In Progress in Roadmap May 5, 2025
@guvenc guvenc merged commit 663d40c into main May 5, 2025
7 checks passed
@guvenc guvenc deleted the feature/dpdk24 branch May 5, 2025 16:50
@github-project-automation github-project-automation bot moved this from In Progress to Done in Roadmap May 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

Update to DPDK 24.11

4 participants