DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Tomasz Kulasek <tomaszx.kulasek@intel.com>
Cc: dev@dpdk.org, Declan Doherty <declan.doherty@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: announce API changes in crypto library
Date: Thu, 11 May 2017 02:51:52 +0200	[thread overview]
Message-ID: <20205816.vbkhsEPyOI@xps> (raw)
In-Reply-To: <afc502c2-70e0-ccf5-aea2-56a415f24699@intel.com>

05/05/2017 17:32, Declan Doherty:
> On 04/05/2017 4:37 PM, Tomasz Kulasek wrote:
> > API changes are planned for 17.08 to made sessions agnostic to the
> > underlaying devices, removing coupling with crypto PMDs, so a single
> > session can be used on multiple devices.
> >
> > It requires to change "struct rte_cryptodev_sym_session" to store more
> > than one private data for devices, as well as remove redundant dev_id
> > and dev_type.
> >
> > Effected public functions:
> >
> >  - rte_cryptodev_sym_session_pool_create
> >  - rte_cryptodev_sym_session_create
> >  - rte_cryptodev_sym_session_free
> >
> > While session will not be directly associated with device, followed API
> > will be changed adding uint8_t dev_id to the argument list:
> >
> >  - rte_cryptodev_queue_pair_attach_sym_session
> >  - rte_cryptodev_queue_pair_detach_sym_session
> >
> > Signed-off-by: Tomasz Kulasek <tomaszx.kulasek@intel.com>
> 
> Acked-by: Declan Doherty <declan.doherty@intel.com>

Applied, thanks

  reply	other threads:[~2017-05-11  0:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-04 15:37 Tomasz Kulasek
2017-05-05 15:32 ` Declan Doherty
2017-05-11  0:51   ` Thomas Monjalon [this message]
2017-05-08  9:49 ` De Lara Guarch, Pablo
2017-05-08 13:54 ` Trahe, Fiona
2017-05-09  8:57 ` 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=20205816.vbkhsEPyOI@xps \
    --to=thomas@monjalon.net \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=tomaszx.kulasek@intel.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).