public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Mounika Kalamandala <mounikax.kalamandala@intel.com>
Cc: dev@dpdk.org, bruce.richardson@intel.com,
	aman.deep.singh@intel.com, shaiq.wani@intel.com
Subject: Re: [PATCH] eal: clean runtime directory files on exit
Date: Fri, 6 Mar 2026 08:34:30 -0800	[thread overview]
Message-ID: <20260306083430.7a0b73a6@phoenix.local> (raw)
In-Reply-To: <20260306060822.328329-1-mounikax.kalamandala@intel.com>

On Fri,  6 Mar 2026 06:08:22 +0000
Mounika Kalamandala <mounikax.kalamandala@intel.com> wrote:

> +    When the primary process exits, all secondary processes must be terminated,
> +    and then restarted after the primary process is re-run to ensure
> +    proper re-initialization of shared resources.
> +    If secondary processes continue running after the primary process
> +    exits, they may experience reduced functionality. In particular,
> +    inter-process communication, new memory allocations, and other
> +    shared infrastructure will no longer be available, which may lead
> +    to unexpected errors.
> +

This wording is a little too soft. There are absolutely no guarantees about
functionality when primary exits. Driver may crash, hardware may be rest.
I would choose stronger language.


  reply	other threads:[~2026-03-06 16:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-06  6:08 [PATCH] eal: clean runtime directory files on exit Mounika Kalamandala
2026-03-06 16:34 ` Stephen Hemminger [this message]
2026-03-06 16:42 ` Stephen Hemminger

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=20260306083430.7a0b73a6@phoenix.local \
    --to=stephen@networkplumber.org \
    --cc=aman.deep.singh@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=mounikax.kalamandala@intel.com \
    --cc=shaiq.wani@intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox