From patchwork Mon Aug 22 14:38:09 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Nithin Dabilpuram X-Patchwork-Id: 115333 X-Patchwork-Delegate: gakhil@marvell.com Return-Path: X-Original-To: patchwork@inbox.dpdk.org Delivered-To: patchwork@inbox.dpdk.org Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id C3DCAA0540; Mon, 22 Aug 2022 16:38:30 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id E1EEB410FA; Mon, 22 Aug 2022 16:38:28 +0200 (CEST) Received: from mx0b-0016f401.pphosted.com (mx0a-0016f401.pphosted.com [67.231.148.174]) by mails.dpdk.org (Postfix) with ESMTP id 7729A410F9 for ; Mon, 22 Aug 2022 16:38:27 +0200 (CEST) Received: from pps.filterd (m0045849.ppops.net [127.0.0.1]) by mx0a-0016f401.pphosted.com (8.17.1.5/8.17.1.5) with ESMTP id 27MDXWOd011931; Mon, 22 Aug 2022 07:38:24 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=marvell.com; h=from : to : cc : subject : date : message-id : in-reply-to : references : mime-version : content-type; s=pfpt0220; bh=j41rwEB4PnLBYm8i7mVw3nMl2TxAX/xGaP4fUzm1S14=; b=Q+MfSRrdzScwjYmoqRnNZQGYllywYpBBSTu6+W/BZIJ6kYibK5qlU+MSx6pWxNjs3dBX rkNHpSSCqv6TtURqfoNLSzQgsG24HCHSPYmFH5/c0JYL3hWjZDhlrk3dsVw2NwZY3/v/ oj5cq3z7eT4luV27qMTVIrSg5ImFcm20gshQ34ZmIslhpx8N0fFi4no058FyLc/CjWzz aZrHJyJ+xD+C1ae9zwdbhIm+42+Dg9RAm+iV68Uq5uKVjUgR6K5JGee/6hIFcGarT4nF SjUtn9wQmUptzb5Bi9enHWwEwhQ9szipCYs52MnywYH0RVbN9fkIuJHeaR+Z3fMjmtB8 0w== Received: from dc5-exch02.marvell.com ([199.233.59.182]) by mx0a-0016f401.pphosted.com (PPS) with ESMTPS id 3j4askg7gm-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 22 Aug 2022 07:38:23 -0700 Received: from DC5-EXCH01.marvell.com (10.69.176.38) by DC5-EXCH02.marvell.com (10.69.176.39) with Microsoft SMTP Server (TLS) id 15.0.1497.18; Mon, 22 Aug 2022 07:38:22 -0700 Received: from maili.marvell.com (10.69.176.80) by DC5-EXCH01.marvell.com (10.69.176.38) with Microsoft SMTP Server id 15.0.1497.2 via Frontend Transport; Mon, 22 Aug 2022 07:38:22 -0700 Received: from hyd1588t430.marvell.com (unknown [10.29.52.204]) by maili.marvell.com (Postfix) with ESMTP id A85653F7058; Mon, 22 Aug 2022 07:38:20 -0700 (PDT) From: Nithin Dabilpuram To: Akhil Goyal CC: , , , "Nithin Dabilpuram" Subject: [PATCH v3 2/5] security: clarify L2 header requirement for outbound inline Date: Mon, 22 Aug 2022 20:08:09 +0530 Message-ID: <20220822143812.30010-2-ndabilpuram@marvell.com> X-Mailer: git-send-email 2.8.4 In-Reply-To: <20220822143812.30010-1-ndabilpuram@marvell.com> References: <20220707072921.13448-1-ndabilpuram@marvell.com> <20220822143812.30010-1-ndabilpuram@marvell.com> MIME-Version: 1.0 X-Proofpoint-GUID: cEF-Y4Cs1A84Ezbapen_wFQ7vOTC8OS2 X-Proofpoint-ORIG-GUID: cEF-Y4Cs1A84Ezbapen_wFQ7vOTC8OS2 X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.205,Aquarius:18.0.895,Hydra:6.0.517,FMLib:17.11.122.1 definitions=2022-08-22_08,2022-08-22_02,2022-06-22_01 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Clarify that for Outbound Inline IPsec processing, L2 header needs to be up to date with ether type which will be applicable post IPsec processing as the IPsec offload only touches L3 and above. Signed-off-by: Nithin Dabilpuram Acked-by: Akhil Goyal --- doc/guides/prog_guide/rte_security.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/doc/guides/prog_guide/rte_security.rst b/doc/guides/prog_guide/rte_security.rst index 72ca0bd..be158f6 100644 --- a/doc/guides/prog_guide/rte_security.rst +++ b/doc/guides/prog_guide/rte_security.rst @@ -146,7 +146,9 @@ adding the relevant protocol headers and encrypting the data before sending the packet out. The software should make sure that the buffer has required head room and tail room for any protocol header addition. The software may also do early fragmentation if the resultant packet is expected -to cross the MTU size. +to cross the MTU size. The software should also make sure that L2 header contents +are updated with the final L2 header which is expected post IPsec processing as +the IPsec offload will only update L3 and above in egress path. .. note::