From: Akhil Goyal <gakhil@marvell.com>
To: Jerin Jacob <jerinjacobk@gmail.com>,
Shijith Thotton <sthotton@marvell.com>
Cc: dpdk-dev <dev@dpdk.org>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Anoob Joseph <anoobj@marvell.com>,
Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>,
Abhinandan Gujjar <abhinandan.gujjar@intel.com>,
Ray Kinsella <mdr@ashroe.eu>,
Ankur Dwivedi <adwivedi@marvell.com>
Subject: Re: [dpdk-dev] [EXT] Re: [PATCH v3] eventdev: update crypto adapter metadata structures
Date: Tue, 7 Sep 2021 08:37:09 +0000 [thread overview]
Message-ID: <CO6PR18MB44841F2D1F54901C118160ADD8D39@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <CALBAE1OjojC82Chds5pPnOw0m3GRZQSxEwN+kMqQ-_tUrZckSA@mail.gmail.com>
> On Tue, Aug 31, 2021 at 1:27 PM Shijith Thotton <sthotton@marvell.com>
> wrote:
> >
> > In crypto adapter metadata, reserved bytes in request info structure is
> > a space holder for response info. It enforces an order of operation if
> > the structures are updated using memcpy to avoid overwriting response
> > info. It is logical to move the reserved space out of request info. It
> > also solves the ordering issue mentioned before.
> >
> > This patch removes the reserve field from request info and makes event
> > crypto metadata type to structure from union to make space for response
> > info.
> >
> > App and drivers are updated as per metadata change.
> >
> > Signed-off-by: Shijith Thotton <sthotton@marvell.com>
> > Acked-by: Anoob Joseph <anoobj@marvell.com>
>
>
> @Gujjar, Abhinandan S @Akhil Goyal
>
> Could you review the crypto adapter-related change?
>
Acked-by: Akhil Goyal <gakhil@marvell.com>
next prev parent reply other threads:[~2021-09-07 8:37 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 18:14 [dpdk-dev] [PATCH] doc: announce change in crypto adapter metadata Shijith Thotton
2021-08-04 18:17 ` Akhil Goyal
2021-08-05 10:12 ` Kinsella, Ray
2021-08-05 10:21 ` Jerin Jacob
2021-08-07 15:10 ` Thomas Monjalon
2021-08-05 2:53 ` [dpdk-dev] [RFC] eventdev: update crypto adapter metadata structures Shijith Thotton
2021-08-30 19:44 ` [dpdk-dev] [PATCH] " Shijith Thotton
2021-08-30 19:59 ` [dpdk-dev] [PATCH v2] " Shijith Thotton
2021-08-31 4:00 ` Anoob Joseph
2021-08-31 6:08 ` Akhil Goyal
2021-08-31 6:51 ` Shijith Thotton
2021-08-31 7:56 ` [dpdk-dev] [PATCH v3] " Shijith Thotton
2021-09-07 8:34 ` Jerin Jacob
2021-09-07 8:37 ` Akhil Goyal [this message]
2021-09-07 8:53 ` Gujjar, Abhinandan S
2021-09-07 10:37 ` Shijith Thotton
2021-09-07 17:30 ` Gujjar, Abhinandan S
2021-09-08 7:42 ` Shijith Thotton
2021-09-08 7:53 ` Gujjar, Abhinandan S
2021-09-14 4:36 ` Shijith Thotton
2021-09-14 4:46 ` Anoob Joseph
2021-09-19 14:25 ` Gujjar, Abhinandan S
2021-09-19 18:49 ` Akhil Goyal
2021-09-20 5:54 ` Gujjar, Abhinandan S
2021-09-27 15:22 ` [dpdk-dev] [PATCH v4] doc: remove event crypto metadata deprecation note Shijith Thotton
2021-09-27 15:29 ` [dpdk-dev] [PATCH] test/event_crypto: fix event crypto metadata write Shijith Thotton
2021-10-03 9:46 ` Gujjar, Abhinandan S
2021-10-05 15:15 ` Akhil Goyal
2021-10-03 9:48 ` [dpdk-dev] [PATCH v4] doc: remove event crypto metadata deprecation note Gujjar, Abhinandan S
2021-10-05 14:49 ` 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=CO6PR18MB44841F2D1F54901C118160ADD8D39@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=abhinandan.gujjar@intel.com \
--cc=adwivedi@marvell.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=mdr@ashroe.eu \
--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).