DPDK patches and discussions
 help / color / mirror / Atom feed
From: Hemant Agrawal <hemant.agrawal@oss.nxp.com>
To: Akhil Goyal <gakhil@marvell.com>, dev@dpdk.org
Cc: thomas@monjalon.net, david.marchand@redhat.com,
	hemant.agrawal@nxp.com, anoobj@marvell.com,
	konstantin.v.ananyev@yandex.ru, ferruh.yigit@xilinx.com,
	andrew.rybchenko@oktetlabs.ru, ndabilpuram@marvell.com,
	vattunuru@marvell.com, matan@nvidia.com, roy.fan.zhang@intel.com,
	jerinj@marvell.com, jiawenwu@trustnetic.com,
	qiming.yang@intel.com
Subject: Re: [PATCH] doc: announce support for MACsec in rte_security
Date: Wed, 29 Jun 2022 09:07:11 +0530	[thread overview]
Message-ID: <728f7330-dacf-4f93-8fba-0bdf608b85a7@oss.nxp.com> (raw)
In-Reply-To: <20220628190802.850690-1-gakhil@marvell.com>


On 6/29/2022 12:38 AM, Akhil Goyal wrote:
> MACsec support is planned for DPDK 22.11, which would
> result in ABI breakage in some of the rte_security structures.
> This patch is to give deprecation notice for the affected structures.
>
> Signed-off-by: Akhil Goyal <gakhil@marvell.com>
> ---
>   doc/guides/rel_notes/deprecation.rst | 5 +++++
>   1 file changed, 5 insertions(+)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> index 4e5b23c53d..1c3bf54d72 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -116,6 +116,11 @@ Deprecation Notices
>     pointer for the private data to the application which can be attached
>     to the packet while enqueuing.
>   
> +* security: MACsec support is planned to be added in DPDK 22.11 which would
> +  result in updates to structures ``rte_security_macsec_xform``,
> +  ``rte_security_macsec_stats`` and security capability structure
> +  ``rte_security_capability`` to accomodate MACsec capabilities.
> +
>   * metrics: The function ``rte_metrics_init`` will have a non-void return
>     in order to notify errors instead of calling ``rte_exit``.
>   
Acked-by:  Hemant Agrawal <hemant.agrawal@nxp.com>

  reply	other threads:[~2022-06-29  3:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 19:08 Akhil Goyal
2022-06-29  3:37 ` Hemant Agrawal [this message]
2022-06-29  7:40 ` Zhang, Roy Fan
2022-07-11 15:00   ` Jerin Jacob
2022-07-17  9:56 ` 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=728f7330-dacf-4f93-8fba-0bdf608b85a7@oss.nxp.com \
    --to=hemant.agrawal@oss.nxp.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=anoobj@marvell.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@xilinx.com \
    --cc=gakhil@marvell.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=jerinj@marvell.com \
    --cc=jiawenwu@trustnetic.com \
    --cc=konstantin.v.ananyev@yandex.ru \
    --cc=matan@nvidia.com \
    --cc=ndabilpuram@marvell.com \
    --cc=qiming.yang@intel.com \
    --cc=roy.fan.zhang@intel.com \
    --cc=thomas@monjalon.net \
    --cc=vattunuru@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).