DPDK usage discussions
 help / color / mirror / Atom feed
From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: Eric Kuha <kuhax005@umn.edu>, "users@dpdk.org" <users@dpdk.org>
Cc: "Trahe, Fiona" <fiona.trahe@intel.com>
Subject: Re: [dpdk-users] Cryptodev asymmetric encryption
Date: Mon, 4 Nov 2019 10:55:50 +0000
Message-ID: <348A99DA5F5B7549AA880327E580B435A218A5FE@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <CAG1M=GCKPvEZ7jR+4byp30LaTHAP8VjDLQ_xDSXpeZoq6-gU1w@mail.gmail.com>

Hi Eric,

> -----Original Message-----
> From: users <users-bounces@dpdk.org> On Behalf Of Eric Kuha
> Sent: Friday, November 1, 2019 4:21 PM
> To: users@dpdk.org
> Subject: [dpdk-users] Cryptodev asymmetric encryption
> Hello,
> I am working with a team at U of MN on a DPDK-based project. We are using DPDK
> 18.11, with Mellanox Connect X-5 EN NICs and mlx5 driver. Not sure what
> other details you might need to help me, but I think my question is
> straightforward enough.
> In the cryptodev library, the function
> rte_cryptodev_asym_get_private_session_size() is flagged as
> __rte_experimental. CLion interprets this as deprecated, which is probably
> neither here nor there. My question is, is this method safe to use? If my
> goal is simply a proof-of-concept network function (of which asymmetric
> crypto is a crucial part), am I safe to use the code used in the examples
> and the programmer's guide? 
[Fiona] yes, it's fine for a proof-of-concept.

If this functionality is going to move out of
> an experimental phase, are they likely to change in significant ways that
> would make my code unusable if it ever makes it to a deployable state?
> And, as a final thought, are any functions listed as __rte_experimental
> considered unsafe for deployment? It might not be an issue for my project,
> but it might be useful to know.
[Fiona] When moving the application to a later DPDK release, there are no guarantees these
APIs will remain the same - so you may need to rework the application to build against the new release.
More information about the experimental label here:

> Kind regards and thanks,
> Eric

      reply	other threads:[~2019-11-04 10:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-01 16:21 Eric Kuha
2019-11-04 10:55 ` Trahe, Fiona [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=348A99DA5F5B7549AA880327E580B435A218A5FE@IRSMSX101.ger.corp.intel.com \
    --to=fiona.trahe@intel.com \
    --cc=kuhax005@umn.edu \
    --cc=users@dpdk.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK usage discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/users/0 users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 users users/ https://inbox.dpdk.org/users \
	public-inbox-index users

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git