From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/DTS Bug 1404] Ensure primary applications such as testpmd are properly cleaned up
Date: Tue, 19 Mar 2024 18:47:53 +0000 [thread overview]
Message-ID: <bug-1404-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1765 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1404
Bug ID: 1404
Summary: Ensure primary applications such as testpmd are
properly cleaned up
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: critical
Priority: Normal
Component: DTS
Assignee: dev@dpdk.org
Reporter: jspewock@iol.unh.edu
CC: juraj.linkes@pantheon.tech, probb@iol.unh.edu
Target Milestone: ---
Right now we are relying on the garbage collector to clean up interactive
shells after they fall out of scope, and this is fine for applications like a
python shell where it doesn't really matter if we run multiple at once.
However, some applications (such as primary applications in DPDK) cannot run if
there is an instance of another specific application running. Because of this,
we need to be able to guarantee that these critical applications close at
certain times but the python garbage collector makes no guarantees for when it
cleans up these objects.
One of the ways to make this more explicit which is being looked into right now
is a context manager. A context manager will help guarantee that when the
application is needed in its context block, it will be running, but as soon as
we exit the block (whether through exceptions being raised, reaching the end of
the block, or anything that would take the code out of that scope) the
application is properly cleaned up. This allows many more guarantees for when
these critical applications are running and exactly when they close.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3712 bytes --]
reply other threads:[~2024-03-19 18:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-1404-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.