* [dpdk-dev] [Bug 447] ixgbe: ixgbe_dev_link_update_share() leaks memory and memory mappings due to not cleaning up pthreads
@ 2020-04-09 17:26 bugzilla
0 siblings, 0 replies; only message in thread
From: bugzilla @ 2020-04-09 17:26 UTC (permalink / raw)
To: dev
https://bugs.dpdk.org/show_bug.cgi?id=447
Bug ID: 447
Summary: ixgbe: ixgbe_dev_link_update_share() leaks memory and
memory mappings due to not cleaning up pthreads
Product: DPDK
Version: 20.02
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: major
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: martin.weiser@allegro-packets.com
Target Milestone: ---
In the patch "net/ixgbe: fix blocking system events"
(819d0d1d57f17aa40321648e99a50b49adc7bdf6) a thread is introduced to
run ixgbe_dev_setup_link_thread_handler().
Unfortunately this thread is not detached and just joined (the very
last one spawned that is) through ixgbe_dev_cancel_link_thread() upon
interface start/stop.
When an application repeatedly calls e.g. rte_eth_link_get_nowait() on
an ixgbe interface with no link this causes a lot of pthreads never to
be cleaned up.
Since each thread holds a mmap to the stack this can quite quickly
exhaust the allowed number of memory mappings for the process.
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2020-04-09 17:28 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-04-09 17:26 [dpdk-dev] [Bug 447] ixgbe: ixgbe_dev_link_update_share() leaks memory and memory mappings due to not cleaning up pthreads bugzilla
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.