DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Gujjar, Abhinandan S" <abhinandan.gujjar@intel.com>
To: Akhil Goyal <akhil.goyal@nxp.com>,
	"jerin.jacob@caviumnetworks.com" <jerin.jacob@caviumnetworks.com>,
	"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Vangati, Narender" <narender.vangati@intel.com>,
	"Rao, Nikhil" <nikhil.rao@intel.com>,
	"Eads, Gage" <gage.eads@intel.com>
Subject: Re: [dpdk-dev] [v4,1/5] eventdev: introduce event crypto adapter
Date: Wed, 9 May 2018 07:26:13 +0000	[thread overview]
Message-ID: <5612CB344B05EE4F95FC5B729939F78070703FD6@PGSMSX102.gar.corp.intel.com> (raw)
In-Reply-To: <479d6bf8-c0aa-620a-1946-0a209a279c59@nxp.com>



> -----Original Message-----
> From: Akhil Goyal [mailto:akhil.goyal@nxp.com]
> Sent: Wednesday, May 9, 2018 12:32 PM
> To: Gujjar, Abhinandan S <abhinandan.gujjar@intel.com>;
> jerin.jacob@caviumnetworks.com; hemant.agrawal@nxp.com;
> akhil.goyal@nxp.com; dev@dpdk.org
> Cc: Vangati, Narender <narender.vangati@intel.com>; Rao, Nikhil
> <nikhil.rao@intel.com>; Eads, Gage <gage.eads@intel.com>
> Subject: Re: [dpdk-dev] [v4,1/5] eventdev: introduce event crypto adapter
> 
> On 5/9/2018 1:16 AM, Abhinandan Gujjar wrote:
> > Signed-off-by: Abhinandan Gujjar <abhinandan.gujjar@intel.com>
> > Signed-off-by: Nikhil Rao <nikhil.rao@intel.com>
> > Signed-off-by: Gage Eads <gage.eads@intel.com>
> > ---
> [...]
> 
> > +
> > +/**
> > + * @warning
> > + * @b EXPERIMENTAL: this structure may change without prior notice
> > + *
> > + * Crypto event metadata structure will be filled by application
> > + * to provide crypto request and event response information.
> > + *
> > + * If crypto events are enqueued using a HW mechanism, the cryptodev
> > + * PMD will use the event response information to set up the event
> > + * that is enqueued back to eventdev after completion of the crypto
> > + * operation. If the transfer is done by SW, event response information
> > + * will be used by the adapter.
> > + */
> > +union rte_event_crypto_metadata {
> > +	struct rte_event_crypto_request request_info;
> > +	/**< Request information to be filled in by application
> > +	 * for RTE_EVENT_CRYPTO_ADAPTER_OP_NEW mode.
> > +	 */
> > +	struct rte_event response_info;
> > +	/**< Response information to be filled in by application
> > +	 * for RTE_EVENT_CRYPTO_ADAPTER_OP_NEW and
> > +	 * RTE_EVENT_CRYPTO_ADAPTER_OP_FORWARD mode.
> > +	 */
> > +};
> I think the comments are not correct. It was correct in previous version.
> request is for only forward mode and response is for both.
Thanks for catching this. I will update this in the next patch.
> 
> Apart from this:
> 
> Patch Series
> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>

  reply	other threads:[~2018-05-09  7:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-08 19:45 [dpdk-dev] [v4,0/5] eventdev: cover letter - " Abhinandan Gujjar
2018-05-08 19:46 ` [dpdk-dev] [v4,1/5] eventdev: introduce event " Abhinandan Gujjar
2018-05-09  2:34   ` Jerin Jacob
2018-05-09  7:01   ` Akhil Goyal
2018-05-09  7:26     ` Gujjar, Abhinandan S [this message]
2018-05-08 19:46 ` [dpdk-dev] [v4, 2/5] eventdev: add APIs and PMD callbacks for " Abhinandan Gujjar
2018-05-09  2:35   ` Jerin Jacob
2018-05-08 19:46 ` [dpdk-dev] [v4,3/5] eventdev: add crypto adapter implementation Abhinandan Gujjar
2018-05-09  2:36   ` [dpdk-dev] [v4, 3/5] " Jerin Jacob
2018-05-08 19:46 ` [dpdk-dev] [v4,4/5] test: add event crypto adapter auto-test Abhinandan Gujjar
2018-05-08 19:46 ` [dpdk-dev] [v4,5/5] doc: add event crypto adapter documentation Abhinandan Gujjar
2018-05-09  2:45   ` [dpdk-dev] [v4, 5/5] " Jerin Jacob

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=5612CB344B05EE4F95FC5B729939F78070703FD6@PGSMSX102.gar.corp.intel.com \
    --to=abhinandan.gujjar@intel.com \
    --cc=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=gage.eads@intel.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=narender.vangati@intel.com \
    --cc=nikhil.rao@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).