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] [v3, 2/5] eventdev: add APIs and PMD callbacks for crypto adapter
Date: Tue, 8 May 2018 08:46:38 +0000 [thread overview]
Message-ID: <5612CB344B05EE4F95FC5B729939F7807070366C@PGSMSX102.gar.corp.intel.com> (raw)
In-Reply-To: <84043fc5-01b4-203e-a173-b596f53d4f62@nxp.com>
> -----Original Message-----
> From: Akhil Goyal [mailto:akhil.goyal@nxp.com]
> Sent: Monday, May 7, 2018 8:59 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] [v3, 2/5] eventdev: add APIs and PMD callbacks for
> crypto adapter
>
> On 5/6/2018 12:17 AM, Abhinandan Gujjar wrote:
> > Signed-off-by: Abhinandan Gujjar <abhinandan.gujjar@intel.com>
> > ---
> > drivers/event/sw/sw_evdev.c | 13 +++
> > lib/librte_eventdev/rte_eventdev.c | 25 +++++
> > lib/librte_eventdev/rte_eventdev.h | 54 ++++++++++
> > lib/librte_eventdev/rte_eventdev_pmd.h | 187
> +++++++++++++++++++++++++++++++++
> > 4 files changed, 279 insertions(+)
> >
> ...
> > +
> > +#define RTE_EVENT_CRYPTO_ADAPTER_CAP_INTERNAL_PORT_OP_FWD
> 0x2
> > +/**< Flag indicates HW is capable of generating events in
> > + * RTE_EVENT_OP_FWD enqueue operation. Cryptodev will send
> The name is RTE_EVENT_OP_FORWARD
Sure. I will update in the next patch.
>
next prev parent reply other threads:[~2018-05-08 8:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-05 18:47 [dpdk-dev] [v3,0/5] eventdev: cover letter - " Abhinandan Gujjar
2018-05-05 18:47 ` [dpdk-dev] [v3,1/5] eventdev: introduce event " Abhinandan Gujjar
2018-05-07 9:35 ` Jerin Jacob
2018-05-07 12:32 ` Akhil Goyal
2018-05-07 13:07 ` Jerin Jacob
2018-05-08 7:34 ` Gujjar, Abhinandan S
2018-05-08 12:49 ` Jerin Jacob
2018-05-08 12:52 ` Gujjar, Abhinandan S
2018-05-05 18:47 ` [dpdk-dev] [v3, 2/5] eventdev: add APIs and PMD callbacks for " Abhinandan Gujjar
2018-05-07 9:52 ` Jerin Jacob
2018-05-08 8:39 ` Gujjar, Abhinandan S
2018-05-07 15:28 ` Akhil Goyal
2018-05-08 8:46 ` Gujjar, Abhinandan S [this message]
2018-05-05 18:47 ` [dpdk-dev] [v3,3/5] eventdev: add crypto adapter implementation Abhinandan Gujjar
2018-05-07 4:58 ` [dpdk-dev] [v3, 3/5] " Jerin Jacob
2018-05-07 6:50 ` Jerin Jacob
2018-05-05 18:47 ` [dpdk-dev] [v3,4/5] test: add event crypto adapter auto-test Abhinandan Gujjar
2018-05-07 5:20 ` Jerin Jacob
2018-05-07 5:58 ` Jerin Jacob
2018-05-07 10:08 ` Jerin Jacob
2018-05-08 8:27 ` Gujjar, Abhinandan S
2018-05-05 18:47 ` [dpdk-dev] [v3,5/5] doc: add event crypto adapter documentation Abhinandan Gujjar
2018-05-07 12:27 ` [dpdk-dev] [v3, 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=5612CB344B05EE4F95FC5B729939F7807070366C@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).