DPDK usage discussions
 help / color / mirror / Atom feed
From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: "users@dpdk.org" <users@dpdk.org>
Cc: "ckdwibedy@gmail.com" <ckdwibedy@gmail.com>,
	"Trahe, Fiona" <fiona.trahe@intel.com>
Subject: Re: [dpdk-users] Question on using crypto library (S/W implementation) with DPDK application
Date: Fri, 5 Aug 2016 14:18:38 +0000	[thread overview]
Message-ID: <348A99DA5F5B7549AA880327E580B435890797A9@IRSMSX101.ger.corp.intel.com> (raw)

Hi Chinmaya,

Sorry for the slow response.

There's a PMD currently under development which may provide what you're looking for.
It will provide 3DES_CBC_128/192 with MD5_HMAC, SHA1/SHA224/SHA256_HMAC and AES-GMAC.
It will translate from dpdk cryptodev API to openssl's libcrypto for the software enablement of these algorithms.

See Tim O'Driscoll's post re 16.11 roadmap on the dev mailing list for more details
http://dpdk.org/ml/archives/dev/2016-July/043534.html




At the moment there are no plans to integrate with AF_ALG.

The performance is unlikely to be satisfactory.



Regards,

Fiona


Hi,

Our application will run on VM (Cloud environment). If access to
crypto acceleration hardware

(besides Intel AES NI/Intel QAT) are not present, what are the
different available choices ?

Do I need to integrate the OpenSSL or Libgcrypt library and invoke
it's APIs from a DPDK application?

Can we use the AF_ALG protocol so as to use the kernels crypto framework?

Please clarify. Thank you in advance for your support and time.



Regards,

Chinmaya

             reply	other threads:[~2016-08-05 14:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-05 14:18 Trahe, Fiona [this message]
2016-08-05 16:05 ` Chinmaya Dwibedy
  -- strict thread matches above, loose matches on Subject: below --
2016-08-02 10:30 Chinmaya Dwibedy
2016-08-04  7:44 ` Chinmaya Dwibedy

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=348A99DA5F5B7549AA880327E580B435890797A9@IRSMSX101.ger.corp.intel.com \
    --to=fiona.trahe@intel.com \
    --cc=ckdwibedy@gmail.com \
    --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).