From mboxrd@z Thu Jan  1 00:00:00 1970
From: Akhil Goyal <akhil.goyal@nxp.com>
Subject: Re: [PATCH v4 00/12] introduce security offload library
Date: Tue, 24 Oct 2017 15:11:59 +0530
Message-ID: <874f0cc6-e42c-792b-88b2-f80dc8ea35b3@nxp.com>
References: <20171006181151.4758-1-akhil.goyal@nxp.com>
 <c0d76c10-21d7-f872-5e21-791220177154@nxp.com>
 <1c66817c-dfe5-4194-0406-57e2da7cdbe4@nxp.com> <26943210.ye3ieRSP5B@xps>
Mime-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 7bit
Cc: <pablo.de.lara.guarch@intel.com>, <radu.nicolau@intel.com>,
 <aviadye@mellanox.com>, <konstantin.ananyev@intel.com>, <dev@dpdk.org>,
 <declan.doherty@intel.com>, <hemant.agrawal@nxp.com>, <borisp@mellanox.com>,
 <sandeep.malik@nxp.com>, <jerin.jacob@caviumnetworks.com>,
 <john.mcnamara@intel.com>, <shahafs@mellanox.com>, <olivier.matz@6wind.com>
To: Thomas Monjalon <thomas@monjalon.net>
Return-path: <dev-bounces@dpdk.org>
Received: from NAM03-CO1-obe.outbound.protection.outlook.com
 (mail-co1nam03on0087.outbound.protection.outlook.com [104.47.40.87])
 by dpdk.org (Postfix) with ESMTP id 1AE9A1B766
 for <dev@dpdk.org>; Tue, 24 Oct 2017 11:42:09 +0200 (CEST)
In-Reply-To: <26943210.ye3ieRSP5B@xps>
Content-Language: en-US
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <http://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: <http://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 Thomas,
On 10/23/2017 2:29 AM, Thomas Monjalon wrote:
> 22/10/2017 22:37, Akhil Goyal:
>> Hi All,
>> On 10/21/2017 9:43 PM, Akhil Goyal wrote:
>>> Hi Thomas,
>>> On 10/20/2017 3:02 PM, Thomas Monjalon wrote:
>>>> 16/10/2017 12:44, Thomas Monjalon:
>>>>> 15/10/2017 00:17, Akhil Goyal:
>>>>>> This patchset introduce the rte_security library in DPDK.
>>>>>> This also includes the sample implementation of drivers and
>>>>>> changes in ipsec gateway application to demonstrate its usage.
>>>>> [...]
>>>>>> This patchset is also available at:
>>>>>> git://dpdk.org/draft/dpdk-draft-ipsec
>>>>>> branch: integration_v4
>>>>>
>>>>> If I understand well, this patchset is the result of the group work?
>>>>> Nothing else is needed to merge for the IPsec offload features?
>>> Yes this patchset is a result of a group work.
>>> We do not need anything else to be merged for ipsec offload features.
>>> But Aviad has made some fixes in the ipsec application which may result
>>> in conflict with the last patch in this series.
>>> So v4 was just rebased over those patches sent by Aviad separately.
>>> We would send a v5 incorporating/answering to all the comments/queries
>>> rebased over the v2 of the Aviad's fixes to the application.
>>>
>>
>> Just for information,
>> I have rebased the rte_security patches over crypto-next and over
>> Aviad's v2. The patches are available at the draft tree
>> "git://dpdk.org/draft/dpdk-draft-ipsec", branch integration_v5.
>>
>> The patchset include the changes suggested by Thomas and Konstantin on v4.
>>
>> The patches are not sent to the mailing list as the ipsec-secgw patches
>> from Aviad needs a v3 and I would like to send the patch set rebased
>> over the v3. I will send the patchset as soon as Aviad's patches are
>> ready to be merged(most probably on Monday).
>>
>> Please let me know in case, there is some risk in getting this series
>> applied in RC2.
> 
> Thanks for the info Akhil.
> A lot of other things are not yet ready for RC2.
> You are still in time.
> 
> 
On which should I base v5 - master or crypto-next?


-Akhil