Adding/removing ports leaks memory in dpdk
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dpdk (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I set up a nicely working OVS-DPDK with KVM Guests.
Then in a loop I
- add up to 512 ports
- test connectivity
- remove up to 512 ports
The effective error is like the issues discussed upstream about >1023 file descriptors - OVS-DPDK crashes due to that.
A lot in the log afterwards are just follow on issues.
But the problem of this bug is that there has to be some sort of leak of file descriptors (or something else depending on analysis).
Because one would expect that adding/removing the same amount of ports should not exceed any "more" of a limit than in the first iteration.
Of 12 planned iterations in 2 of 2 tries I now always failed at iteration 6.
So I hope it is rather reproducible and will start debugging it.
---
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
DistroRelease: Ubuntu 16.04
Package: openvswitch-dpdk
PackageArchitec
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
Tags: xenial uec-images
Uname: Linux 4.4.0-18-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: kvm libvirtd
_MarkForUpload: True
modified.
modified.
mtime.conffile.
mtime.conffile.
Changed in dpdk (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in openvswitch-dpdk (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → ChristianEhrhardt (paelzer) |
Changed in dpdk (Ubuntu): | |
importance: | Medium → High |
summary: |
- Adding removing/ports leaks file descriptors + Adding removing/ports leaks memory |
summary: |
- Adding removing/ports leaks memory + Adding removing/ports leaks memory in dpdk |
no longer affects: | openvswitch-dpdk (Ubuntu) |
summary: |
- Adding removing/ports leaks memory in dpdk + Adding/removing ports leaks memory in dpdk |
tags: |
added: verification-done removed: verification-needed |
Further analysis indicates more a memory leak or issues of allocation due to fragmentation.
Adding report...