DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Chaoyong He <chaoyong.he@corigine.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: oss-drivers <oss-drivers@corigine.com>
Subject: Re: [PATCH v2 00/10] add the support of ipsec offload
Date: Thu, 28 Sep 2023 10:33:26 +0100	[thread overview]
Message-ID: <ea6127e8-71f1-436d-ae71-aae2c23d8ee4@amd.com> (raw)
In-Reply-To: <SJ0PR13MB55454946068A0688ADB352709EC1A@SJ0PR13MB5545.namprd13.prod.outlook.com>

On 9/28/2023 3:05 AM, Chaoyong He wrote:
>> On 9/26/2023 3:49 AM, Chaoyong He wrote:
>>> This patch series add the support of ipsec offload feature, includes:
>>> * Implement the communication channel between PMD and firmware through
>>>   mailbox.
>>> * Implement the ipsec offload related APIs based the security framework.
>>> * Implement the ipsec packets process logics in the data path.
>>>
>>> ---
>>> v2:
>>> * Fix one spell error cause check warning.
>>> * Try to fix one compile error in Alpine environment of CI.
>>> ---
>>>
>>> Chang Miao (2):
>>>   net/nfp: initialize IPsec related content
>>>   net/nfp: create security session
>>>
>>> Shihong Wang (8):
>>>   mailmap: update contributor entry
>>>   net/nfp: add TLVs capability parsing
>>>   net/nfp: add mailbox to support IPsec offload
>>>   net/nfp: get security capabilities and session size
>>>   net/nfp: get IPsec Rx/Tx packet statistics
>>>   net/nfp: update security session
>>>   net/nfp: support IPsec Rx and Tx offload
>>>   net/nfp: destroy security session
>>>
>>
>> Hi Chaoyong,
>>
>> Patchset looks good, but adding ipsec support to driver seems significant enough
>> to document in the release notes, what do you think?
> 
> Yeah, I agree. I will try to add that in the next version.
> A separate commit for that or squash that into the final commit of this patch series,
> which one you think is better?
>

Squashing to the most relevant commit it better,
this creates a link between the documentation and the code which is
useful when back tracing a feature in the git history.


  reply	other threads:[~2023-09-28  9:33 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-25  6:06 [PATCH " Chaoyong He
2023-09-25  6:06 ` [PATCH 01/10] mailmap: update contributor entry Chaoyong He
2023-09-27 14:19   ` Ferruh Yigit
2023-09-28  1:50     ` Chaoyong He
2023-09-25  6:06 ` [PATCH 02/10] net/nfp: add TLVs capability parsing Chaoyong He
2023-09-27 14:19   ` Ferruh Yigit
2023-09-28  2:02     ` Chaoyong He
2023-09-28  9:30       ` Ferruh Yigit
2023-09-25  6:06 ` [PATCH 03/10] net/nfp: add mailbox to support IPsec offload Chaoyong He
2023-09-25  6:06 ` [PATCH 04/10] net/nfp: initialize IPsec related content Chaoyong He
2023-09-25  6:06 ` [PATCH 05/10] net/nfp: get security capabilities and session size Chaoyong He
2023-09-25  6:06 ` [PATCH 06/10] net/nfp: get IPsec Rx/Tx packet statistics Chaoyong He
2023-09-25  6:06 ` [PATCH 07/10] net/nfp: create security session Chaoyong He
2023-09-25  6:06 ` [PATCH 08/10] net/nfp: update " Chaoyong He
2023-09-25  6:06 ` [PATCH 09/10] net/nfp: support IPsec Rx and Tx offload Chaoyong He
2023-09-25  6:06 ` [PATCH 10/10] net/nfp: destroy security session Chaoyong He
2023-09-26  2:49 ` [PATCH v2 00/10] add the support of ipsec offload Chaoyong He
2023-09-26  2:49   ` [PATCH v2 01/10] mailmap: update contributor entry Chaoyong He
2023-09-26  2:49   ` [PATCH v2 02/10] net/nfp: add TLVs capability parsing Chaoyong He
2023-09-26  2:49   ` [PATCH v2 03/10] net/nfp: add mailbox to support IPsec offload Chaoyong He
2023-09-26  2:49   ` [PATCH v2 04/10] net/nfp: initialize IPsec related content Chaoyong He
2023-09-26  2:49   ` [PATCH v2 05/10] net/nfp: get security capabilities and session size Chaoyong He
2023-09-26  2:49   ` [PATCH v2 06/10] net/nfp: get IPsec Rx/Tx packet statistics Chaoyong He
2023-09-26  2:49   ` [PATCH v2 07/10] net/nfp: create security session Chaoyong He
2023-09-26  2:49   ` [PATCH v2 08/10] net/nfp: update " Chaoyong He
2023-09-26  2:49   ` [PATCH v2 09/10] net/nfp: support IPsec Rx and Tx offload Chaoyong He
2023-09-26  2:49   ` [PATCH v2 10/10] net/nfp: destroy security session Chaoyong He
2023-09-27 14:20   ` [PATCH v2 00/10] add the support of ipsec offload Ferruh Yigit
2023-09-28  2:05     ` Chaoyong He
2023-09-28  9:33       ` Ferruh Yigit [this message]
2023-09-29  2:08   ` [PATCH v3 0/9] " Chaoyong He
2023-09-29  2:08     ` [PATCH v3 1/9] net/nfp: add TLVs capability parsing Chaoyong He
2023-09-29  2:08     ` [PATCH v3 2/9] net/nfp: add mailbox to support IPsec offload Chaoyong He
2023-09-29  2:08     ` [PATCH v3 3/9] net/nfp: initialize IPsec related content Chaoyong He
2023-09-29 10:00       ` Ferruh Yigit
2023-09-29  2:08     ` [PATCH v3 4/9] net/nfp: get security capabilities and session size Chaoyong He
2023-09-29  2:08     ` [PATCH v3 5/9] net/nfp: get IPsec Rx/Tx packet statistics Chaoyong He
2023-09-29  2:08     ` [PATCH v3 6/9] net/nfp: create security session Chaoyong He
2023-09-29  2:08     ` [PATCH v3 7/9] net/nfp: update " Chaoyong He
2023-09-29  2:08     ` [PATCH v3 8/9] net/nfp: support IPsec Rx and Tx offload Chaoyong He
2023-09-29  2:08     ` [PATCH v3 9/9] net/nfp: destroy security session Chaoyong He
2023-09-29 10:05     ` [PATCH v3 0/9] add the support of ipsec offload Ferruh Yigit

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=ea6127e8-71f1-436d-ae71-aae2c23d8ee4@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=chaoyong.he@corigine.com \
    --cc=dev@dpdk.org \
    --cc=oss-drivers@corigine.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).