From: Raslan Darawsheh <rasland@nvidia.com>
To: Bing Zhao <bingz@nvidia.com>, Matan Azrad <matan@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Ori Kam <orika@nvidia.com>, Suanming Mou <suanmingm@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>,
"David Marchand" <david.marchand@redhat.com>,
"Mário Kuka" <kuka@cesnet.cz>
Subject: RE: [PATCH v2] net/mlx5: fix the drop action memory leak
Date: Tue, 18 Jul 2023 11:58:16 +0000 [thread overview]
Message-ID: <BYAPR12MB3078D2BA2BB5A552B2E9F7A8CF38A@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230713111941.427361-1-bingz@nvidia.com>
,
x
> -----Original Message-----
> From: Bing Zhao <bingz@nvidia.com>
> Sent: Thursday, July 13, 2023 2:20 PM
> To: Matan Azrad <matan@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Ori Kam <orika@nvidia.com>; Suanming Mou
> <suanmingm@nvidia.com>; Raslan Darawsheh <rasland@nvidia.com>
> Cc: dev@dpdk.org; stable@dpdk.org; David Marchand
> <david.marchand@redhat.com>; Mário Kuka <kuka@cesnet.cz>
> Subject: [PATCH v2] net/mlx5: fix the drop action memory leak
>
> In DV mode, when quitting an application, the default drop action
> and its resources should be released. The Devx action for the TIR
> was not destroyed and it would cause 80B memory leak.
>
> With this commit, in DV mode, the action should be destroyed in the
> mlx5_devx_drop_action_destroy() explicitly.
>
> Bugzilla ID: 1192
> Bugzilla ID: 1255
>
> Fixes: bc5bee028ebc ("net/mlx5: create drop queue using DevX")
> Cc: stable@dpdk.org
>
> Reported-by: David Marchand <david.marchand@redhat.com>
> Reported-by: Mário Kuka<kuka@cesnet.cz>
> Signed-off-by: Bing Zhao <bingz@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> ---
> v2: added the reporter
Patch applied to next-net-mlx,
Kindest regards
Raslan Darawsheh
prev parent reply other threads:[~2023-07-18 11:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 11:06 [PATCH] " Bing Zhao
2023-07-13 11:19 ` [PATCH v2] " Bing Zhao
2023-07-18 11:58 ` Raslan Darawsheh [this message]
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=BYAPR12MB3078D2BA2BB5A552B2E9F7A8CF38A@BYAPR12MB3078.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=bingz@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=kuka@cesnet.cz \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=stable@dpdk.org \
--cc=suanmingm@nvidia.com \
--cc=viacheslavo@nvidia.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;
as well as URLs for NNTP newsgroup(s).