From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>, <dev@dpdk.org>
Cc: <stable@dpdk.org>, Qi Zhang <qi.z.zhang@intel.com>
Subject: Re: [PATCH 2/2] eal: notify secondary on primary exit
Date: Wed, 23 Sep 2026 15:04:41 +0200 [thread overview]
Message-ID: <99a1f01d-ec36-4399-a82b-6e477819416d@intel.com> (raw)
In-Reply-To: <20260507210152.410419-3-stephen@networkplumber.org>
On 5/7/2026 10:58 PM, Stephen Hemminger wrote:
> When primary process exits, it should notify the secondary
> processes. This allows for clean shutdown and eliminates need
> for MP handling in applications (such as test-pmd).
>
> Bugzilla ID: 1942
> Fixes: 85d6815fa6d0 ("eal: close multi-process socket during cleanup")
> Cc: stable@dpdk.org
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
It would be cool to have some kind of event for this so that processes
could react to primary/secondary going up/down, but this is 1) way
beyond scope of this patch, and 2) of dubious usefulness given that the
only thing testpmd did with the information was to stop forwarding.
--
Thanks,
Anatoly
next prev parent reply other threads:[~2026-09-23 13:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 20:58 [PATCH 0/2] eal: notify secondaries on primary exit Stephen Hemminger
2026-05-07 20:58 ` [PATCH 1/2] Revert "app/testpmd: stop forwarding in secondary process" Stephen Hemminger
2026-09-23 13:02 ` Burakov, Anatoly
2026-05-07 20:58 ` [PATCH 2/2] eal: notify secondary on primary exit Stephen Hemminger
2026-09-23 13:04 ` Burakov, Anatoly [this message]
2026-06-18 16:09 ` [PATCH 0/2] eal: notify secondaries " Stephen Hemminger
2026-10-07 21:17 ` Thomas Monjalon
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=99a1f01d-ec36-4399-a82b-6e477819416d@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.com \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.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.