DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Vamsi Attunuru <vattunuru@marvell.com>
Cc: dev@dpdk.org, jerinj@marvell.com, vattunuru@marvell.com,
	gakhil@marvell.com, ferruh.yigit@intel.com, anoobj@marvell.com,
	mdr@ashroe.eu
Subject: Re: [PATCH v2 1/1] doc: announce addition of new ipsec event subtypes
Date: Tue, 12 Jul 2022 17:03:30 +0200	[thread overview]
Message-ID: <6043248.xgNZFEDtJV@thomas> (raw)
In-Reply-To: <20220627052937.759050-1-vattunuru@marvell.com>

27/06/2022 07:29, Vamsi Attunuru:
> New event subtypes need to be added for notifying expiry events
> upon reaching IPsec SA soft packet expiry and hard packet/byte
> expiry limits. This would be added in DPDK 22.11.
> 
> Signed-off-by: Vamsi Attunuru <vattunuru@marvell.com>
> Acked-by: Akhil Goyal <gakhil@marvell.com>
> ---
> More details on new event subtype proposal discussion are in below email thread.
> https://patches.dpdk.org/project/dpdk/patch/20220416192530.173895-8-gakhil@marvell.com/
> 
> v2: rephrase title and git log.
> ---
> +* ethdev: The enum ``rte_eth_event_ipsec_subtype`` would be extended to add
> +  new subtype values ``RTE_ETH_EVENT_IPSEC_SA_PKT_EXPIRY``,
> +  ``RTE_ETH_EVENT_IPSEC_SA_BYTE_HARD_EXPIRY`` and
> +  ``RTE_ETH_EVENT_IPSEC_SA_PKT_HARD_EXPIRY`` in DPDK 22.11.

While at it, would you consider avoiding future ABI breakage
with RTE_ETH_EVENT_IPSEC_MAX?




  parent reply	other threads:[~2022-07-12 15:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24 13:35 [PATCH 1/1] doc: notice to add " Vamsi Attunuru
2022-06-24 18:18 ` Akhil Goyal
2022-06-27  5:29 ` [PATCH v2 1/1] doc: announce addition of " Vamsi Attunuru
2022-07-06  9:49   ` Zhang, Roy Fan
2022-07-11 14:53     ` Jerin Jacob
2022-07-12 11:44       ` Andrew Rybchenko
2022-07-17 10:07         ` Thomas Monjalon
2022-07-12 15:03   ` Thomas Monjalon [this message]
2022-07-12 15:30     ` [EXT] " Akhil Goyal
2022-07-12 20:44       ` 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=6043248.xgNZFEDtJV@thomas \
    --to=thomas@monjalon.net \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=gakhil@marvell.com \
    --cc=jerinj@marvell.com \
    --cc=mdr@ashroe.eu \
    --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).