From: Mohammad Abdul Awal <mohammad.abdul.awal@intel.com>
To: Konstantin Ananyev <konstantin.ananyev@intel.com>, dev@dpdk.org
Cc: akhil.goyal@nxp.com, declan.doherty@intel.com
Subject: Re: [dpdk-dev] [PATCH] doc: security deprecation notice for session changes
Date: Wed, 14 Nov 2018 11:32:11 +0000 [thread overview]
Message-ID: <ea4ee743-1bed-209a-cd77-56b1273ea768@intel.com> (raw)
In-Reply-To: <1542194611-5773-1-git-send-email-konstantin.ananyev@intel.com>
On 14/11/2018 11:23, Konstantin Ananyev wrote:
> Add 'uint64_t opaque_data' inside struct rte_security_session.
> That allows upper layer to easily associate some user defined
> data with the session.
> Proposed new layout for:
> struct rte_security_session {
> void *sess_private_data;
> /**< Private session material */
> + uint64_t opaque_data;
> + /**< Opaque user defined data */
> };
>
> Signed-off-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
> ---
> doc/guides/rel_notes/deprecation.rst | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> index 34b28234c..0cdc42842 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -55,3 +55,9 @@ Deprecation Notices
> - ``rte_pdump_set_socket_dir`` will be removed;
> - The parameter, ``path``, of ``rte_pdump_init`` will be removed;
> - The enum ``rte_pdump_socktype`` will be removed.
> +
> +* security: ABI change:
> +
> + New field ``uint64_t opaque_data`` is planned to add into
> + ``rte_security_session`` structure. That would allow upper layer to easily
> + associate/de-associate some user defined data with the security session.
Acked-by: Mohammad Abdul Awal <mohammad.abdul.awal@intel.com>
next prev parent reply other threads:[~2018-11-14 11:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 11:23 Konstantin Ananyev
2018-11-14 11:32 ` Mohammad Abdul Awal [this message]
2018-11-14 11:32 ` Zhang, Roy Fan
2018-11-14 12:39 ` Akhil Goyal
2018-11-14 13:02 ` Ananyev, Konstantin
2018-11-24 17:59 ` Thomas Monjalon
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=ea4ee743-1bed-209a-cd77-56b1273ea768@intel.com \
--to=mohammad.abdul.awal@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@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).