From: Akhil Goyal <gakhil@marvell.com>
To: Michael Baum <michaelba@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [EXT] [PATCH] crypto/mlx5: fix indirect mkey cleaning
Date: Fri, 24 Sep 2021 17:50:51 +0000 [thread overview]
Message-ID: <CO6PR18MB4484183B0DE3F3468670A7CCD8A49@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20210913191646.612617-1-michaelba@nvidia.com>
> The driver creates an indirect mkey per entry in the queue to manage the
> crypto operation using the BSF fields.
>
> The indirect mkeys were never released neither while error occurs in the
> creation phase nor when the queue is released.
>
> Clean the indirect mkeys in the above cases.
>
> Fixes: c2a42d19d967 ("crypto/mlx5: add WQE set initialization")
> Cc: stable@dpdk.org
>
> Signed-off-by: Michael Baum <michaelba@nvidia.com>
> Acked-by: Matan Azrad <matan@nvidia.com>
Applied to dpdk-next-crypto
prev parent reply other threads:[~2021-09-24 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 19:16 [dpdk-dev] " Michael Baum
2021-09-24 17:50 ` Akhil Goyal [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=CO6PR18MB4484183B0DE3F3468670A7CCD8A49@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=michaelba@nvidia.com \
--cc=stable@dpdk.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 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).