DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Abhinandan Gujjar <abhinandan.gujjar@intel.com>,
	pablo.de.lara.guarch@intel.com, declan.doherty@intel.com,
	jerin.jacob@caviumnetworks.com, hemant.agrawal@nxp.com,
	dev@dpdk.org
Cc: narender.vangati@intel.com, nikhil.rao@intel.com
Subject: Re: [dpdk-dev] [dpdk-dev, v1, 3/3] doc: update cryptodev documentation for set/get private data
Date: Tue, 10 Apr 2018 14:51:57 +0530	[thread overview]
Message-ID: <41e3bfb1-22ce-f359-0969-e8edec7bd9dc@nxp.com> (raw)
In-Reply-To: <1522823672-60023-1-git-send-email-abhinandan.gujjar@intel.com>

Hi Abhinandan,

One minor comment.
Series
Acked-by: Akhil Goyal <akhil.goyal@nxp.com>

On 4/4/2018 12:04 PM, Abhinandan Gujjar wrote:
> Signed-off-by: Abhinandan Gujjar <abhinandan.gujjar@intel.com>
> ---
>   doc/guides/prog_guide/cryptodev_lib.rst | 26 ++++++++++++++++++++++++++
>   1 file changed, 26 insertions(+)
> 
> diff --git a/doc/guides/prog_guide/cryptodev_lib.rst b/doc/guides/prog_guide/cryptodev_lib.rst
> index 066fe2d..57b3f6e 100644
> --- a/doc/guides/prog_guide/cryptodev_lib.rst
> +++ b/doc/guides/prog_guide/cryptodev_lib.rst
> @@ -299,6 +299,32 @@ directly from the devices processed queue, and for virtual device's from a
>   enqueue call.
>   
>   
> +Set/Get private data
> +~~~~~~~~~~~~~~~~~~~~
> +For session-based operations, the set and get API provides a mechanism for an
> +application to store and retrieve the private data information stored along with
> +the rte_cryptodev_sym_session session.
> +
> +For example, suppose an application is submitting a rte_cryptodev_sym_session
> +operation and wants to indicate private data information is required to be used
wants to indicate private data information which is required

> +after completion of the rte_cryptodev_sym_session operation. In this case, the
> +application can use the set API to set the private data and retrieve it using get API.
> +
> +.. code-block:: c
> +
> +	int rte_cryptodev_sym_session_set_private_data(
> +		struct rte_cryptodev_sym_session *sess,	void *data, uint16_t size);
> +
> +	void * rte_cryptodev_sym_session_get_private_data(
> +		struct rte_cryptodev_sym_session *sess);
> +
> +
> +For session-less mode, the private data information can be placed along with the
> +``struct rte_crypto_op``. The ``rte_crypto_op::private_data_offset`` indicates the start
> +of private data information. The offset is counted from the start of the rte_crypto_op
> +including initialization vector (IV).
> +
> +
>   Enqueue / Dequeue Burst APIs
>   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>   
> 

  reply	other threads:[~2018-04-10  9:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-04  6:34 Abhinandan Gujjar
2018-04-10  9:21 ` Akhil Goyal [this message]
2018-04-12  6:30   ` Gujjar, Abhinandan S
2018-04-13 19:07 ` De Lara Guarch, Pablo

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=41e3bfb1-22ce-f359-0969-e8edec7bd9dc@nxp.com \
    --to=akhil.goyal@nxp.com \
    --cc=abhinandan.gujjar@intel.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=narender.vangati@intel.com \
    --cc=nikhil.rao@intel.com \
    --cc=pablo.de.lara.guarch@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).