From: Brandon Lo <blo@iol.unh.edu>
To: Akhil Goyal <gakhil@marvell.com>
Cc: Shijith Thotton <sthotton@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>, "ci@dpdk.org" <ci@dpdk.org>,
Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>,
Anoob Joseph <anoobj@marvell.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
"abhinandan.gujjar@intel.com" <abhinandan.gujjar@intel.com>,
Ankur Dwivedi <adwivedi@marvell.com>
Subject: Re: [dpdk-dev] [dpdk-ci] [PATCH v2 2/2] drivers: add octeontx crypto adapter data path
Date: Wed, 30 Jun 2021 12:23:09 -0400 [thread overview]
Message-ID: <CAOeXdvbOEZZ4V7aNrsmmaF5038FEAM1_cVgpCD-C1et92UBKOw@mail.gmail.com> (raw)
In-Reply-To: <CO6PR18MB4484106B5ABB0BB27FCAFFDAD8019@CO6PR18MB4484.namprd18.prod.outlook.com>
Hi Akhil,
I believe the FreeBSD 13 failure appeared because new requirements
were added for drivers/event/octeontx.
The ABI reference was taken at the v21.05 release which was able to
build this driver at the time.
I will try to look for a way to produce a real ABI test.
Thanks,
Brandon
On Wed, Jun 30, 2021 at 4:54 AM Akhil Goyal <gakhil@marvell.com> wrote:
>
> > Added support for crypto adapter OP_FORWARD mode.
> >
> > As OcteonTx CPT crypto completions could be out of order, each crypto op
> > is enqueued to CPT, dequeued from CPT and enqueued to SSO one-by-one.
> >
> > Signed-off-by: Shijith Thotton <sthotton@marvell.com>
> > ---
> This patch shows a CI warning for FreeBSD, but was not able to locate the error/warning in the logs.
> Can anybody confirm what is the issue?
>
> http://mails.dpdk.org/archives/test-report/2021-June/200637.html
>
> Regards,
> Akhil
--
Brandon Lo
UNH InterOperability Laboratory
21 Madbury Rd, Suite 100, Durham, NH 03824
blo@iol.unh.edu
www.iol.unh.edu
next prev parent reply other threads:[~2021-06-30 16:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 16:48 [dpdk-dev] [PATCH 0/2] OCTEONTX crypto adapter support Shijith Thotton
2021-06-22 16:48 ` [dpdk-dev] [PATCH 1/2] drivers: add octeontx crypto adapter framework Shijith Thotton
2021-06-22 16:48 ` [dpdk-dev] [PATCH 2/2] drivers: add octeontx crypto adapter data path Shijith Thotton
2021-07-06 20:20 ` Akhil Goyal
2021-06-23 20:53 ` [dpdk-dev] [PATCH v2 0/2] OCTEONTX crypto adapter support Shijith Thotton
2021-06-23 20:53 ` [dpdk-dev] [PATCH v2 1/2] drivers: add octeontx crypto adapter framework Shijith Thotton
2021-07-06 20:14 ` Akhil Goyal
2021-07-15 14:21 ` David Marchand
2021-07-16 8:39 ` [dpdk-dev] [EXT] " Akhil Goyal
2021-07-20 11:58 ` Akhil Goyal
2021-07-20 12:14 ` David Marchand
2021-07-21 9:44 ` Thomas Monjalon
2021-07-21 15:11 ` Brandon Lo
2021-07-22 7:45 ` Akhil Goyal
2021-07-22 9:06 ` [dpdk-dev] [PATCH] crypto/octeontx: enable build on non Linux OS Shijith Thotton
2021-07-22 9:17 ` Akhil Goyal
2021-07-22 19:06 ` Thomas Monjalon
2021-07-22 19:08 ` Thomas Monjalon
2021-07-22 20:20 ` Brandon Lo
2021-07-22 20:32 ` Thomas Monjalon
2021-06-23 20:53 ` [dpdk-dev] [PATCH v2 2/2] drivers: add octeontx crypto adapter data path Shijith Thotton
2021-06-30 8:54 ` Akhil Goyal
2021-06-30 16:23 ` Brandon Lo [this message]
2021-07-07 9:28 ` [dpdk-dev] [PATCH v2 0/2] OCTEONTX crypto adapter support Akhil Goyal
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=CAOeXdvbOEZZ4V7aNrsmmaF5038FEAM1_cVgpCD-C1et92UBKOw@mail.gmail.com \
--to=blo@iol.unh.edu \
--cc=abhinandan.gujjar@intel.com \
--cc=adwivedi@marvell.com \
--cc=anoobj@marvell.com \
--cc=ci@dpdk.org \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--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).