From: Anoob Joseph <anoobj@marvell.com>
To: Thierry Herbelot <thierry.herbelot@6wind.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>,
"stable@dpdk.org" <stable@dpdk.org>,
Akhil Goyal <akhil.goyal@nxp.com>,
"Jerin Jacob Kollanukkaran" <jerinj@marvell.com>,
Narayana Prasad Raju Athreya <pathreya@marvell.com>
Subject: Re: [dpdk-dev] [EXT] [PATCH V2] crypto/octeontx: enable unbinding for the OCTEON TX crypto engines
Date: Fri, 13 Sep 2019 06:58:53 +0000 [thread overview]
Message-ID: <BN8PR18MB2868D87E24B36E58383E4424DFB30@BN8PR18MB2868.namprd18.prod.outlook.com> (raw)
In-Reply-To: <15217f0aa7b041c895dd1a956e703bb48df6c453.1568356742.git.thierry.herbelot@6wind.com>
Version history has to be after ---.
@Akhil, can you make this change when you submit?
Acked-by: Anoob Joseph <anoobj@marvell.com>
> -----Original Message-----
> From: Thierry Herbelot <thierry.herbelot@6wind.com>
> Sent: Friday, September 13, 2019 12:10 PM
> To: dev@dpdk.org
> Cc: Thomas Monjalon <thomas@monjalon.net>; stable@dpdk.org; Anoob
> Joseph <anoobj@marvell.com>
> Subject: [EXT] [PATCH V2] crypto/octeontx: enable unbinding for the OCTEON
> TX crypto engines
>
> External Email
>
> ----------------------------------------------------------------------
> Like for Ethernet ports, the OCTEON TX crypto engines must first be unbound
> from their kernel module, then rebound to vfio-pci, before being usable in DPDK.
>
> As this capability is detected at runtime by dpdk-pmdinfo, add the info in the
> PMD registering directives.
>
> Then an external script can be used for bind and unbind.
>
> Fixes: bfe2ae495ee268 ('crypto/octeontx: add PMD skeleton')
> Cc: stable@dpdk.org
> Cc: anoobj@marvell.com
>
> V2: only "vfio-pci" is needed by this PMD
>
> Signed-off-by: Thierry Herbelot <thierry.herbelot@6wind.com>
> ---
> drivers/crypto/octeontx/otx_cryptodev.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/crypto/octeontx/otx_cryptodev.c
> b/drivers/crypto/octeontx/otx_cryptodev.c
> index fc64a5f3041f..8df4b710c874 100644
> --- a/drivers/crypto/octeontx/otx_cryptodev.c
> +++ b/drivers/crypto/octeontx/otx_cryptodev.c
> @@ -118,6 +118,7 @@ static struct cryptodev_driver otx_cryptodev_drv;
>
> RTE_PMD_REGISTER_PCI(CRYPTODEV_NAME_OCTEONTX_PMD,
> otx_cryptodev_pmd);
> RTE_PMD_REGISTER_PCI_TABLE(CRYPTODEV_NAME_OCTEONTX_PMD,
> pci_id_cpt_table);
> +RTE_PMD_REGISTER_KMOD_DEP(CRYPTODEV_NAME_OCTEONTX_PMD,
> "vfio-pci");
> RTE_PMD_REGISTER_CRYPTO_DRIVER(otx_cryptodev_drv,
> otx_cryptodev_pmd.driver,
> otx_cryptodev_driver_id);
>
> --
> 2.20.1
next prev parent reply other threads:[~2019-09-13 6:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 16:07 [dpdk-dev] [PATCH] drivers/crypto/octeontx: enable unbinding for the OcteonTx " Thierry Herbelot
2019-09-12 16:37 ` [dpdk-dev] [EXT] " Anoob Joseph
2019-09-13 6:40 ` [dpdk-dev] [PATCH V2] crypto/octeontx: enable unbinding for the OCTEON TX " Thierry Herbelot
2019-09-13 6:58 ` Anoob Joseph [this message]
2019-09-19 15:14 ` [dpdk-dev] [EXT] " 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=BN8PR18MB2868D87E24B36E58383E4424DFB30@BN8PR18MB2868.namprd18.prod.outlook.com \
--to=anoobj@marvell.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=pathreya@marvell.com \
--cc=stable@dpdk.org \
--cc=thierry.herbelot@6wind.com \
--cc=thomas@monjalon.net \
/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).