From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 01B7EA0C43; Tue, 28 Sep 2021 17:46:40 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id C0EFA410D7; Tue, 28 Sep 2021 17:46:40 +0200 (CEST) Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) by mails.dpdk.org (Postfix) with ESMTP id A583840E3C for ; Tue, 28 Sep 2021 17:46:39 +0200 (CEST) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 6C77F3201D32; Tue, 28 Sep 2021 11:46:38 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Tue, 28 Sep 2021 11:46:38 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=fm2; bh= JzGNEgCvURVBUyStbhlSzkScKAsV7V+D1gfu0aBknN8=; b=obgjkJhEDaEXtwwE 4UuAL72CXtNvdUKE/G5jvh/gjX604vfFPr7wt39qbce6Mj2p9k723Eku2kms/xzV oxZuARcnCK7Mabt/5isd6GEIlHzQ8h+Zy+wDkB/r3wQ4J8nGb/0IIe/49qGoY2AM FOnVR73m/vQ6AHfsLWrid/lUJ7lbVDfGch+z1nlc/1n6Vm5XwamcDpjqxpcNYmpg uIw/U9EODP9XaD1g9vmv8EQ8QYL4LeaKG0zKWVvRVFWYlyzC50wPRxMIWiqEHJTG c1MTuHIHy5Pu6hRb3lKziYPoJ3pkJ52vz62r10H9zUI4eyPo5VTts8ElVzWm3imv KirV/Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=JzGNEgCvURVBUyStbhlSzkScKAsV7V+D1gfu0aBkn N8=; b=vRqss6ehACJd1+OWPp8mlZORqXOI7BDmY79sxfgpZbeJb/neEfa+MrbpI MO64y6KrVk4QRitY1lbW0ihWO2nklwteF2mvn7PqxHQlybQaEQORbN2wE7Tavz1w e7w1pgx8x8NmrED4w7Tr85mKvM4/VZK5mj/JKyyhF6VXZT/SnJTjGtFa7b5I1OXN mXpy+JhCB+Sh1CsXtiRofCsuL3Vm9nC2mpBMaYHDjTg8k7YmgBscnq4VjeBumCoq +8Y9Hfb9PQdkVntNcL/5Q7J9A309puqhs3kSEN+tLnxNCUMJ9Dyur878mt46aANN 86aADW9WjDC1m/rJQF52QEOCN/E5A== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrudektddgkeelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnhepudeggfdvfeduffdtfeeglefghfeukefgfffhueejtdetuedtjeeu ieeivdffgeehnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 28 Sep 2021 11:46:37 -0400 (EDT) From: Thomas Monjalon To: Venkat Duvvuru , Ajit Khaparde , Ferruh Yigit Cc: dev@dpdk.org, Kishore Padmanabha , "jerinj@marvell.com" Date: Tue, 28 Sep 2021 17:46:35 +0200 Message-ID: <2245188.ABCaCfflTv@thomas> In-Reply-To: <043f9e39-222d-975d-d361-f9b27e7a3c74@intel.com> References: <20210908050643.9989-1-venkatkumar.duvvuru@broadcom.com> <20210920074214.23747-7-venkatkumar.duvvuru@broadcom.com> <043f9e39-222d-975d-d361-f9b27e7a3c74@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v4 06/13] net/bnxt: add support for tunnel offload API 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 Sender: "dev" 28/09/2021 14:43, Ferruh Yigit: > On 9/20/2021 8:42 AM, Venkat Duvvuru wrote: > > From: Kishore Padmanabha > > > > Add support for tunnel offload APIs. Specifically the following > > are supported. > > tunnel_decap_set, tunnel_match, tunnel_action_decap_release, > > tunnel_item_release. > > > > This provides support for VXLAN decap action where two flows > > can indicate tunnel offload rule. The first flow indicates the > > tunnel properties and second flow indicates the inner packet > > structure. The templates are updated to support this > > feature. > > > > Signed-off-by: Kishore Padmanabha > > Signed-off-by: Venkat Duvvuru > > Reviewed-by: Shahaji Bhosle > > Acked-by: Ajit Khaparde > > > Hi Ajit, > > Following warning is reported by Jerin & Thomas: > > $ ./devtools/check-doc-vs-code.sh > rte_flow doc out of sync for bnxt > action shared > > > This is mainly saying 'RTE_FLOW_ACTION_TYPE_SHARED' flow action is supported but > not documented. But from code I am not sure if shared action is used, there is > only one range check using this enum in the code, can you please clarify? > If it is supported I can update the documentation. Please fix it in the right commit atomically.