From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: Suraj R Gupta <surajrgupta@iith.ac.in>,
"users@dpdk.org" <users@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-users] [Crypto-PMD and Libraries] Suggestions on porting/attaching existing libraries with Crypto PMDS
Date: Mon, 13 May 2019 10:03:30 +0000 [thread overview]
Message-ID: <348A99DA5F5B7549AA880327E580B43589763ACD@IRSMSX101.ger.corp.intel.com> (raw)
Message-ID: <20190513100330.8vAiUcLJ8HyMy9FHlTSHPVEzqaXtUNmU3vo8DoelTro@z> (raw)
In-Reply-To: <CAMfGv3kYeUmZBsQQ8nySVQaX5-7eh+kp9MDgF7A=i91uGr-kog@mail.gmail.com>
Hi Suraj,
> -----Original Message-----
> From: users [mailto:users-bounces@dpdk.org] On Behalf Of Suraj R Gupta
> Sent: Monday, May 13, 2019 6:11 AM
> To: users@dpdk.org; dev@dpdk.org
> Subject: [dpdk-users] [dpdk-dev] [Crypto-PMD and Libraries] Suggestions on porting/attaching existing
> libraries with Crypto PMDS
>
> Hi,
> This is in regards with using Cryptographic libraries with DPDK crypto
> PMDs. Intel has its own Cryptographic libraries for various algorithms
> hosted in git and some restricted channels.
> I would like to know if any other library can be attached to the Crypto Pmd.
>
> For e.g. I would like to know if any Kasumi algorithm library can be
> attached with Kasumi Crypto PMD.
[Fiona] No, the kasumi software PMD is essentially a shim between the
DPDK cryptodev API and the Intel libsso_kasumi library.
If you have another KASUMI library that you want to use you should
create a new PMD to wrap that library.
> I would like to have your suggestions and help in this regard.
>
> --
> Thanks and Regards
> Suraj R Gupta
next prev parent reply other threads:[~2019-05-13 10:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 5:11 [dpdk-dev] " Suraj R Gupta
2019-05-13 5:11 ` Suraj R Gupta
2019-05-13 10:03 ` Trahe, Fiona [this message]
2019-05-13 10:03 ` [dpdk-dev] [dpdk-users] " Trahe, Fiona
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=348A99DA5F5B7549AA880327E580B43589763ACD@IRSMSX101.ger.corp.intel.com \
--to=fiona.trahe@intel.com \
--cc=dev@dpdk.org \
--cc=surajrgupta@iith.ac.in \
--cc=users@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).