From: Akhil Goyal <akhil.goyal@nxp.com>
To: Junxiao Shi <git@mail1.yoursunny.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "pablo.de.lara.guarch@intel.com" <pablo.de.lara.guarch@intel.com>,
"Trahe, Fiona" <fiona.trahe@intel.com>,
Shally Verma <shallyv@marvell.com>,
"anoobj@marvell.com" <anoobj@marvell.com>
Subject: Re: [dpdk-dev] [PATCH] cryptodev: free memzone when releasing cryptodev
Date: Thu, 27 Jun 2019 14:03:01 +0000 [thread overview]
Message-ID: <VE1PR04MB6639EA86783945E46EF22ADBE6FD0@VE1PR04MB6639.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <201905301724.x4UHOJN7016223@lectura.cs.arizona.edu>
>
> When a cryptodev is created in a primary process,
> rte_cryptodev_data_alloc reserves a memzone.
> However, this memzone was not released when the cryptodev
> is uninitialized. After that, new cryptodev cannot be
> created due to memzone name conflict.
>
> This commit frees the memzone when a cryptodev is
> uninitialized, fixing this bug. This approach is chosen
> instead of keeping and reusing the old memzone, because
> the new cryptodev could belong to a different NUMA socket.
>
> Also, rte_cryptodev_data pointer is now properly recorded
> in cryptodev_globals.data array.
>
> Bugzilla ID: 105
>
> Signed-off-by: Junxiao Shi <git@mail1.yoursunny.com>
> ---
Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
next prev parent reply other threads:[~2019-06-27 14:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 17:07 Junxiao Shi
2019-06-27 14:03 ` Akhil Goyal [this message]
2019-06-28 5:46 ` [dpdk-dev] [EXT] " Anoob Joseph
2019-06-28 6:15 ` Akhil Goyal
2019-06-28 7:03 ` Anoob Joseph
2019-06-28 7:09 ` Anoob Joseph
2019-06-28 19:11 ` [dpdk-dev] [PATCH v2] " Junxiao Shi
2019-07-01 11:48 ` Akhil Goyal
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=VE1PR04MB6639EA86783945E46EF22ADBE6FD0@VE1PR04MB6639.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=git@mail1.yoursunny.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=shallyv@marvell.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).