All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Fidaullah Noonari <fidaullah.noonari@emumba.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v2] app/proc-info: add rte_eal_cleanup() to avoid memory leak
Date: Sun, 16 Jul 2023 10:46:33 -0700	[thread overview]
Message-ID: <20230716104633.5af3a28d@hermes.local> (raw)
In-Reply-To: <20220904122845.141893-1-fidaullah.noonari@emumba.com>

On Sun,  4 Sep 2022 17:28:45 +0500
Fidaullah Noonari <fidaullah.noonari@emumba.com> wrote:

> when app is launched with -m proc-info exit without
> rte_eal_cleanup() causing memory leakage. This commit resolves the
> memory leakage issue and closes app properly.
> 
> Bugzilla id: 898

The new eventdev stats could have the same problem.

Acked-by: Stephen Hemminger <stephen@networkplumber.org>

  reply	other threads:[~2023-07-16 17:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-04 12:28 [PATCH v2] app/proc-info: add rte_eal_cleanup() to avoid memory leak Fidaullah Noonari
2023-07-16 17:46 ` Stephen Hemminger [this message]
2024-10-04  2:48 ` [PATCH v3] " Stephen Hemminger
2024-10-09  1:22   ` fengchengwen
2024-11-19 20:51     ` 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=20230716104633.5af3a28d@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=fidaullah.noonari@emumba.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 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.