Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes for regressions in max-next headed for Octarina release #1466

Merged
merged 8 commits into from
Jan 21, 2022

Conversation

eugeneia
Copy link
Member

@eugeneia eugeneia commented Jan 20, 2022

This fixes a performance regression caught while running the benchmark matrix for the Octarina release. See 247ef95 and 5f045e7.

Also includes a fix for a test regression of lwAFTR, see 992a845.

eugeneia and others added 8 commits January 13, 2022 15:58
…ctions

Recent changes ([1], [2], [3]) exposed some previously internal variables
and functions from core.packet. This patch restores local bindings for
those within core.packet in order to maintain performance.

[1] 6174563 (snabbco#1450)
[2] ee4e42d (snabbco#1450)
[3] 9f0694f (snabbco#1288)
lwAFTR introduced a way to run applications with vmprofile disabled,
in a way that branched on engine.vmprofile_enabled on the fast path.

This patch cleans this up to only disable the profiler timer,
and run setvmprofile unconditionally in both cases.

Also removes the duplicate/unused/ineffectual profile option
from lib.ptree.worker (profiling can be disabled via lib.scheduling).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant