From: Akhil Goyal <akhil.goyal@nxp.com>
To: dev@dpdk.org
Cc: hemant.agrawal@nxp.com, pablo.de.lara.guarch@intel.com,
abhinandan.gujjar@intel.com,
Jerin Jacob <jerin.jacob@caviumnetworks.com>
Subject: Re: [dpdk-dev] [PATCH 0/3] dpaa2: support for crypto adapter
Date: Tue, 9 Oct 2018 18:52:28 +0530 [thread overview]
Message-ID: <545ed90d-95f7-91cd-c91e-bbaf3d139966@nxp.com> (raw)
In-Reply-To: <20180914114810.14960-1-akhil.goyal@nxp.com>
On 9/14/2018 5:18 PM, akhil.goyal@nxp.com wrote:
> From: Akhil Goyal <akhil.goyal@nxp.com>
>
> This patchset add support for event crypto adapter on dpaa2_sec
> support for parallel and atomic queues are added.
>
> The patches are rebased over
> http://patches.dpdk.org/user/todo/dpdk/?series=1101
>
>
>
> Akhil Goyal (2):
> crypto/dpaa2_sec: support for event crypto adapter
> event/dpaa2: support for crypto adapter
>
> Ashish Jain (1):
> crypto/dpaa2_sec: support for atomic queues
>
> drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c | 145 ++++++++++++++++-
> drivers/crypto/dpaa2_sec/dpaa2_sec_event.h | 18 +++
> drivers/crypto/dpaa2_sec/dpaa2_sec_priv.h | 2 +
> .../dpaa2_sec/rte_pmd_dpaa2_sec_version.map | 8 +
> drivers/event/dpaa2/Makefile | 3 +-
> drivers/event/dpaa2/dpaa2_eventdev.c | 150 ++++++++++++++++++
> drivers/event/dpaa2/dpaa2_eventdev.h | 9 ++
> drivers/event/dpaa2/meson.build | 3 +-
> 8 files changed, 330 insertions(+), 8 deletions(-)
> create mode 100644 drivers/crypto/dpaa2_sec/dpaa2_sec_event.h
>
Applied to dpdk-next-crypto
prev parent reply other threads:[~2018-10-09 13:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 11:48 akhil.goyal
2018-09-14 11:48 ` [dpdk-dev] [PATCH 1/3] crypto/dpaa2_sec: support for event " akhil.goyal
2018-09-14 11:48 ` [dpdk-dev] [PATCH 2/3] crypto/dpaa2_sec: support for atomic queues akhil.goyal
2018-09-14 11:48 ` [dpdk-dev] [PATCH 3/3] event/dpaa2: support for crypto adapter akhil.goyal
2018-09-25 3:11 ` Jerin Jacob
2018-10-02 9:49 ` Gujjar, Abhinandan S
2018-10-09 13:22 ` Akhil Goyal [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:
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=545ed90d-95f7-91cd-c91e-bbaf3d139966@nxp.com \
--to=akhil.goyal@nxp.com \
--cc=abhinandan.gujjar@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@caviumnetworks.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).