From mboxrd@z Thu Jan  1 00:00:00 1970
From: Anoob Joseph <Anoob.Joseph@caviumnetworks.com>
Subject: Re: [PATCH v2 2/5] lib/security: add ESN soft limit in
	conf
Date: Wed, 14 Mar 2018 10:45:24 +0530
Message-ID: <01f8faa9-edde-7a0b-9b12-8e43376a929d@caviumnetworks.com>
References: <1519191430-19201-1-git-send-email-anoob.joseph@caviumnetworks.com>
 <1519896103-32479-1-git-send-email-anoob.joseph@caviumnetworks.com>
 <1519896103-32479-3-git-send-email-anoob.joseph@caviumnetworks.com>
 <ef7c7e5d-5643-0d88-75c4-598d0021bd68@nxp.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Jerin Jacob <jerin.jacob@caviumnetworks.com>,
 Narayana Prasad <narayanaprasad.athreya@caviumnetworks.com>,
 Nelio Laranjeiro <nelio.laranjeiro@6wind.com>, dev@dpdk.org
To: Akhil Goyal <akhil.goyal@nxp.com>,
 Declan Doherty <declan.doherty@intel.com>,
 Radu Nicolau <radu.nicolau@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from NAM01-BN3-obe.outbound.protection.outlook.com
 (mail-bn3nam01on0048.outbound.protection.outlook.com [104.47.33.48])
 by dpdk.org (Postfix) with ESMTP id 95717271
 for <dev@dpdk.org>; Wed, 14 Mar 2018 06:15:45 +0100 (CET)
In-Reply-To: <ef7c7e5d-5643-0d88-75c4-598d0021bd68@nxp.com>
Content-Language: en-US
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

Hi Akhil,

Will revise the patch with the mentioned change.

Thanks,
Anoob

On 13/03/18 17:49, Akhil Goyal wrote:
> Hi Anoob,
>
> Just a minor comment.
> On 3/1/2018 2:51 PM, Anoob Joseph wrote:
>> Adding ESN soft limit in conf. This will be used in case of protocol
>> offload. Per SA, application could specify for what ESN the security
>> device need to notify application. In case of eth dev(inline protocol),
>> rte_eth_event framework would raise an IPsec event.
>>
>> Signed-off-by: Anoob Joseph <anoob.joseph@caviumnetworks.com>
>> ---
>> v2:
>> * No change
>>
>>   lib/librte_security/rte_security.h | 2 ++
>>   1 file changed, 2 insertions(+)
>>
>> diff --git a/lib/librte_security/rte_security.h 
>> b/lib/librte_security/rte_security.h
>> index c75c121..a71ff6f 100644
>> --- a/lib/librte_security/rte_security.h
>> +++ b/lib/librte_security/rte_security.h
>> @@ -222,6 +222,8 @@ struct rte_security_ipsec_xform {
>>       /**< IPsec SA Mode - transport/tunnel */
>>       struct rte_security_ipsec_tunnel_param tunnel;
>>       /**< Tunnel parameters, NULL for transport mode */
>> +    uint64_t esn_soft_limit;
>> +    /**< ESN for which the overflow event need to be raised by eth 
>> dev */
>
> eth/crypto dev
>
>>   };
>>     /**
>>
>