From: Jerin Jacob <jerinjacobk@gmail.com>
To: Shijith Thotton <sthotton@marvell.com>
Cc: dpdk-dev <dev@dpdk.org>, Jerin Jacob <jerinj@marvell.com>,
Anoob Joseph <anoobj@marvell.com>,
Ankur Dwivedi <adwivedi@marvell.com>,
Pavan Nikhilesh <pbhagavatula@marvell.com>
Subject: Re: [dpdk-dev] [PATCH v2 0/2] event/octeontx2: fixes for crypto adapter
Date: Thu, 29 Apr 2021 14:20:38 +0530 [thread overview]
Message-ID: <CALBAE1PmJcfvR+Q4F2HsMxhYa9XHSssfLYOdv-3ME3a9xiUmmw@mail.gmail.com> (raw)
In-Reply-To: <cover.1619439044.git.sthotton@marvell.com>
On Mon, Apr 26, 2021 at 5:51 PM Shijith Thotton <sthotton@marvell.com> wrote:
>
> Fixes for OCTEON TX2 crypto adapter implementation.
>
> v2:
> - Fixed adapter xae count updation.
Series applied to dpdk-next-net-eventdev/for-main. Thanks
>
> Shijith Thotton (2):
> event/octeontx2: fix crypto adapter queue pair ops
> event/octeontx2: configure crypto adapter xaq pool
>
> drivers/crypto/octeontx2/otx2_cryptodev_qp.h | 4 +-
> drivers/event/octeontx2/otx2_evdev_adptr.c | 2 +-
> .../event/octeontx2/otx2_evdev_crypto_adptr.c | 110 +++++++++++++-----
> 3 files changed, 84 insertions(+), 32 deletions(-)
>
> --
> 2.25.1
>
prev parent reply other threads:[~2021-04-29 8:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 19:10 [dpdk-dev] [PATCH v1 " Shijith Thotton
2021-04-15 19:10 ` [dpdk-dev] [PATCH v1 1/2] event/octeontx2: fix crypto adapter queue pair ops Shijith Thotton
2021-04-15 19:10 ` [dpdk-dev] [PATCH v1 2/2] event/octeontx2: configure crypto adapter xaq pool Shijith Thotton
2021-04-26 10:17 ` Pavan Nikhilesh Bhagavatula
2021-04-26 12:21 ` [dpdk-dev] [PATCH v2 0/2] event/octeontx2: fixes for crypto adapter Shijith Thotton
2021-04-26 12:21 ` [dpdk-dev] [PATCH v2 1/2] event/octeontx2: fix crypto adapter queue pair ops Shijith Thotton
2021-04-26 14:44 ` Ankur Dwivedi
2021-04-26 12:21 ` [dpdk-dev] [PATCH v2 2/2] event/octeontx2: configure crypto adapter xaq pool Shijith Thotton
2021-04-29 8:50 ` Jerin Jacob [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=CALBAE1PmJcfvR+Q4F2HsMxhYa9XHSssfLYOdv-3ME3a9xiUmmw@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=adwivedi@marvell.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=pbhagavatula@marvell.com \
--cc=sthotton@marvell.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).