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

Merge with lwaftr v2019.06.01 #1448

Merged
merged 110 commits into from
Nov 8, 2019
Merged

Merge with lwaftr v2019.06.01 #1448

merged 110 commits into from
Nov 8, 2019

Conversation

eugeneia
Copy link
Member

@eugeneia eugeneia commented Nov 4, 2019

See Igalia#1234

[2019.06.01]

Notable changes

wingo and others added 30 commits February 21, 2019 16:56
* lib/ljsyscall/syscall/linux/syscalls.lua: More robustly create
  multi-word bitmasks.

* src/lib/numa.lua: Remove facility for blacklisting kernel versions.
  Re-enable bind_to_numa_node generally.
This commit makes four changes:

  (1) On the individual revision nodes in a schema, the revision date is
      now stored under `date` instead of `value`.

  (2) Schemas now have a `last_revision` property, indicating the date
      of the most recent revision.

  (3) This revision now gets serialized into compiled configurations.

  (4) When loading compiled configurations, we check that the compiled
      file's revision date corresponds to the what we are expecting.

Fixes #1208.
The file in question is too small for the minimum ethernet frame size;
with the CRC it becomes 58 bytes, which is smaller than the minimum
frame size of 64, so it gets padded as it goes out on the wire, which
later gets rejected on the receiver as its lengths don't make sense.  In
any case it doesn't test what it means to test, so remove it.
Remove bogus lwaftr benchmarking file
Detect version mismatch when loading compiled YANG configurations
Re-enable NUMA memory binding on newer kernels
Fix PCI affinity check for --preferred NUMA binding
This patch extends the NUMA module to be able to run some self-checks
when it is used to reserve a CPU for a data plane, for example checking
the CPU frequency scaling governor or the set of isolated CPUs.
Add more system performance diagnostics
This patch will print a warning if a network function tries to bind
to a CPU, but irqbalance is detected.  Irqbalance, installed by default
on Debian-derived systems, will modify CPU affinities for IRQ
handlers in an effort to spread out the IRQ-processing load among
CPUs.  However this is not what we want in Snabb; we do not want
data-plane CPUs to run IRQ handlers, and we do not want bug reports
coming from users that have this daemon installed.

See https://github.com/snabbco/snabb/blob/master/src/doc/performance-tuning.md#avoid-interrupts-on-data-plane-cpus, for more details.
Detect irqbalance presence and suggest remedy
Improve snabb lwaftr run --help
…ering differences between v4 and v6 packets. Stop in a more robust way.
Start ingress drop monitor in grace period
Refactor "snabb packetblaster lwaftr" to re-use base apps
Bump snabb-softwire-v2 revision date
wingo and others added 25 commits October 14, 2019 16:40
Fix promotion of lib.fibers.timer events from outer to inner wheel
lib.ptree: do not aggregate (ignore) counters that are symlinks
The ptree worker will automatically install a heap size monitor,
which writes to engine/heap_size_bytes.{gauge,rrd}.
Make memory monitor a timer instead of an app
…ter-symlinks

Revert "lib.ptree: do not aggregate (ignore) counters that are symlinks"
Add `snabb rrdcat' tool to summarize RRD archives
Plug various resource leaks in context of (re)configuration
…r-queue

timers.ingress_drop_monitor: use app:get_rxstats() (was app:rxdrop())
Fix release benchmarks to always specify CPU
@lukego
Copy link
Member

lukego commented Nov 4, 2019

Could you possibly pull next and resolve the conflict in snabb-softwire-v2.lua?

eugeneia added a commit to eugeneia/snabb that referenced this pull request Nov 4, 2019
@eugeneia eugeneia added the merged label Nov 4, 2019
@eugeneia eugeneia merged commit c5191f6 into snabbco:master Nov 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants