From: Suanming Mou <suanmingm@nvidia.com>
To: Bing Zhao <bingz@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Raslan Darawsheh <rasland@nvidia.com>
Cc: Ori Kam <orika@nvidia.com>,
Dariusz Sosnowski <dsosnowski@nvidia.com>,
Matan Azrad <matan@nvidia.com>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
Roi Dayan <roid@nvidia.com>,
Gregory Etelson <getelson@nvidia.com>
Subject: RE: [PATCH 2/4] common/mlx5: release unused mempool entries
Date: Wed, 12 Nov 2025 08:38:12 +0000 [thread overview]
Message-ID: <CH2PR12MB954482294BCAD23174A31A56C1CCA@CH2PR12MB9544.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20251112074131.8929-1-bingz@nvidia.com>
> -----Original Message-----
> From: Bing Zhao <bingz@nvidia.com>
> Sent: Wednesday, November 12, 2025 3:42 PM
> To: Slava Ovsiienko <viacheslavo@nvidia.com>; dev@dpdk.org; Raslan
> Darawsheh <rasland@nvidia.com>
> Cc: Ori Kam <orika@nvidia.com>; Dariusz Sosnowski
> <dsosnowski@nvidia.com>; Suanming Mou <suanmingm@nvidia.com>;
> Matan Azrad <matan@nvidia.com>; NBU-Contact-Thomas Monjalon
> (EXTERNAL) <thomas@monjalon.net>; Bing Zhao <bingz@nvidia.com>; Roi
> Dayan <roid@nvidia.com>; Gregory Etelson <getelson@nvidia.com>
> Subject: [PATCH 2/4] common/mlx5: release unused mempool entries
>
> From: Roi Dayan <roid@nvidia.com>
>
> When creating a new mempool but assigning a shared entries from a different
> mempool need to release the newly unused allocated entries. Fix it.
>
> Fixes: 8947eebc999e ("common/mlx5: fix shared memory region ranges
> allocation")
> Cc: bingz@nvidia.com
>
> Signed-off-by: Roi Dayan <roid@nvidia.com>
> Signed-off-by: Gregory Etelson <getelson@nvidia.com>
Acked-by: Suanming Mou <suanmingm@nvidia.com>
prev parent reply other threads:[~2025-11-12 8:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 7:41 Bing Zhao
2025-11-12 8:38 ` Suanming Mou [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=CH2PR12MB954482294BCAD23174A31A56C1CCA@CH2PR12MB9544.namprd12.prod.outlook.com \
--to=suanmingm@nvidia.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=getelson@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=roid@nvidia.com \
--cc=thomas@monjalon.net \
--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).