From: Shijith Thotton <sthotton@marvell.com>
To: <dev@dpdk.org>
Cc: Shijith Thotton <sthotton@marvell.com>,
<abhinandan.gujjar@intel.com>, <adwivedi@marvell.com>,
<anoobj@marvell.com>, <gakhil@marvell.com>, <jerinj@marvell.com>,
<pbhagavatula@marvell.com>
Subject: [dpdk-dev] [PATCH v4] doc: remove event crypto metadata deprecation note
Date: Mon, 27 Sep 2021 20:52:44 +0530 [thread overview]
Message-ID: <2c543df71bc79ff363c1aa501e0bf5a88cb448a7.1632731708.git.sthotton@marvell.com> (raw)
In-Reply-To: <f7cd7ff7559b56ff6496e54bf63c94ce15232b48.1630396445.git.sthotton@marvell.com>
Proposed change to event crypto metadata is not done as per deprecation
note. Instead, comments are updated in spec to improve readability.
Signed-off-by: Shijith Thotton <sthotton@marvell.com>
---
v4:
* Removed changes as per deprecation note.
* Updated spec comments.
v3:
* Updated ABI section of release notes.
v2:
* Updated deprecation notice.
v1:
* Rebased.
doc/guides/rel_notes/deprecation.rst | 6 ------
lib/eventdev/rte_event_crypto_adapter.h | 1 +
2 files changed, 1 insertion(+), 6 deletions(-)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index bf1e07c0a8..fae3abd282 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -254,12 +254,6 @@ Deprecation Notices
An 8-byte reserved field will be added to the structure ``rte_event_timer`` to
support future extensions.
-* eventdev: Reserved bytes of ``rte_event_crypto_request`` is a space holder
- for ``response_info``. Both should be decoupled for better clarity.
- New space for ``response_info`` can be made by changing
- ``rte_event_crypto_metadata`` type to structure from union.
- This change is targeted for DPDK 21.11.
-
* metrics: The function ``rte_metrics_init`` will have a non-void return
in order to notify errors instead of calling ``rte_exit``.
diff --git a/lib/eventdev/rte_event_crypto_adapter.h b/lib/eventdev/rte_event_crypto_adapter.h
index 27fb628eef..edbd5c61a3 100644
--- a/lib/eventdev/rte_event_crypto_adapter.h
+++ b/lib/eventdev/rte_event_crypto_adapter.h
@@ -227,6 +227,7 @@ union rte_event_crypto_metadata {
struct rte_event_crypto_request request_info;
/**< Request information to be filled in by application
* for RTE_EVENT_CRYPTO_ADAPTER_OP_FORWARD mode.
+ * First 8 bytes of request_info is reserved for response_info.
*/
struct rte_event response_info;
/**< Response information to be filled in by application
--
2.25.1
next prev parent reply other threads:[~2021-09-27 15:23 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 ` [dpdk-dev] [EXT] " Akhil Goyal
2021-09-07 8:53 ` [dpdk-dev] " 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 ` Shijith Thotton [this message]
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=2c543df71bc79ff363c1aa501e0bf5a88cb448a7.1632731708.git.sthotton@marvell.com \
--to=sthotton@marvell.com \
--cc=abhinandan.gujjar@intel.com \
--cc=adwivedi@marvell.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=jerinj@marvell.com \
--cc=pbhagavatula@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).