From: Ferruh Yigit <ferruh.yigit@xilinx.com>
To: Vamsi Krishna Attunuru <vattunuru@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>, Anoob Joseph <anoobj@marvell.com>,
Konstantin Ananyev <konstantin.ananyev@intel.com>
Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>,
Akhil Goyal <gakhil@marvell.com>
Subject: Re: [PATCH 1/1] ethdev: add packet expiry event subtype
Date: Wed, 20 Apr 2022 19:16:00 +0100 [thread overview]
Message-ID: <4607ff89-ee9a-73c3-d3fe-53c8c3c84d5f@xilinx.com> (raw)
In-Reply-To: <MWHPR18MB0942EB15BEE43249AABA91BEA6189@MWHPR18MB0942.namprd18.prod.outlook.com>
On 3/23/2022 3:04 AM, Vamsi Krishna Attunuru wrote:
> Ping..
>
>> -----Original Message-----
>> From: Vamsi Attunuru <vattunuru@marvell.com>
>> Sent: Thursday, March 17, 2022 1:28 PM
>> To: dev@dpdk.org
>> Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>; Nithin Kumar
>> Dabilpuram <ndabilpuram@marvell.com>; Akhil Goyal
>> <gakhil@marvell.com>; Vamsi Krishna Attunuru <vattunuru@marvell.com>
>> Subject: [PATCH 1/1] ethdev: add packet expiry event subtype
>>
>> Patch adds a new event subtype for notifying expiry event upon soft packet
>> limit expiry.
>>
cc'ed more people
Is there any user of this event to provide more context? Or to justify
why it is needed?
>> Signed-off-by: Vamsi Attunuru <vattunuru@marvell.com>
>> ---
>> lib/ethdev/rte_ethdev.h | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/lib/ethdev/rte_ethdev.h b/lib/ethdev/rte_ethdev.h index
>> 04cff8ee10..07d1f02bae 100644
>> --- a/lib/ethdev/rte_ethdev.h
>> +++ b/lib/ethdev/rte_ethdev.h
>> @@ -3828,6 +3828,8 @@ enum rte_eth_event_ipsec_subtype {
>> RTE_ETH_EVENT_IPSEC_SA_TIME_EXPIRY,
>> /** Soft byte expiry of SA */
>> RTE_ETH_EVENT_IPSEC_SA_BYTE_EXPIRY,
>> + /** Soft packet expiry of SA */
>> + RTE_ETH_EVENT_IPSEC_SA_PKT_EXPIRY,
>> /** Max value of this enum */
>> RTE_ETH_EVENT_IPSEC_MAX
>> };
>> @@ -3849,6 +3851,7 @@ struct rte_eth_event_ipsec_desc {
>> * - @ref RTE_ETH_EVENT_IPSEC_ESN_OVERFLOW
>> * - @ref RTE_ETH_EVENT_IPSEC_SA_TIME_EXPIRY
>> * - @ref RTE_ETH_EVENT_IPSEC_SA_BYTE_EXPIRY
>> + * - @ref RTE_ETH_EVENT_IPSEC_SA_PKT_EXPIRY
>> *
>> * @see struct rte_security_session_conf
>> *
>> --
>> 2.25.1
>
next prev parent reply other threads:[~2022-04-20 18:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 7:57 Vamsi Attunuru
2022-03-23 3:04 ` Vamsi Krishna Attunuru
2022-04-20 18:16 ` Ferruh Yigit [this message]
2022-04-21 6:45 ` [EXT] " Vamsi Krishna Attunuru
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=4607ff89-ee9a-73c3-d3fe-53c8c3c84d5f@xilinx.com \
--to=ferruh.yigit@xilinx.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=jerinj@marvell.com \
--cc=konstantin.ananyev@intel.com \
--cc=ndabilpuram@marvell.com \
--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).