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 46F24A0547; Tue, 28 Sep 2021 23:32:48 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id CB22D410D7; Tue, 28 Sep 2021 23:32:47 +0200 (CEST) Received: from mail-io1-f50.google.com (mail-io1-f50.google.com [209.85.166.50]) by mails.dpdk.org (Postfix) with ESMTP id 9751A40E3C for ; Tue, 28 Sep 2021 23:32:46 +0200 (CEST) Received: by mail-io1-f50.google.com with SMTP id r75so422809iod.7 for ; Tue, 28 Sep 2021 14:32:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=7SFFF7o13e7mk/lHbeqT0JmkFNyB5djUVNVm0AfXIXE=; b=KfuJfKRwnwYcyf9ZO1Cfu7hMHaJ3kyQwOGbangOC3aOlWGj4B3URcS5gzw8T+mBlkD yNvdET14Rjp3WzKaZflJJzRFMgkXIkkIsgxqunHyLTuagjhd3JcoEc+zG5VYFb5nQgsS oNlAEQablUe6YGhVXzn1iac7kObBeLEXVD2SQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=7SFFF7o13e7mk/lHbeqT0JmkFNyB5djUVNVm0AfXIXE=; b=SpcXhOrnjMRf+OLt+PLG70rN+WZ2xC6I52S0S056PPdpxkFv387FSF+2y5y2ZBp/mm 8LyBXMP8p3QY4Nazx5lpqVPKMtpkFMeV8xpG5L8fDNVleP0YECEk9bmPof2bHDliHJBX ZkFupVrVHM8Q+AboS6kwwMYogz1G5tvGAEeE3eqP9FSUNDsAbYivn5mah1+5DnZGdHE4 yiS/x/t7bJi5AcMbRC/hMC7GR9/p3JcPKgUyr1gnWtGH3+is1wg4YfD030NiQJH1g9eX fexFvsDog8TswTfNtp0Wgr/IGxjqhdWR0i1bO3Z5GW15gL9xAZ7sAKUO12+uzvf3aFeV ks4w== X-Gm-Message-State: AOAM530KjeWmIHvTB2wSiEr3fvT+IKrxzfHIS1vIVyM7L1BoUmMBOADa y43QbdnwNCtZT0lTlY/U6w9UNiqjoQ03jmdXBQnw+w== X-Google-Smtp-Source: ABdhPJztYeP3ktalgWpHeKsxcd37xPaAoQ0onVHdVKi1DwMb3KY+LpuWspk7o+RIOVw5f6IW0OBa/Gf0Sgt9fg2bfAg= X-Received: by 2002:a05:6638:d43:: with SMTP id d3mr6457640jak.60.1632864765826; Tue, 28 Sep 2021 14:32:45 -0700 (PDT) MIME-Version: 1.0 References: <20210908050643.9989-1-venkatkumar.duvvuru@broadcom.com> <20210920074214.23747-1-venkatkumar.duvvuru@broadcom.com> <20210920074214.23747-7-venkatkumar.duvvuru@broadcom.com> <043f9e39-222d-975d-d361-f9b27e7a3c74@intel.com> In-Reply-To: <043f9e39-222d-975d-d361-f9b27e7a3c74@intel.com> From: Ajit Khaparde Date: Tue, 28 Sep 2021 14:32:29 -0700 Message-ID: To: Ferruh Yigit Cc: Venkat Duvvuru , dpdk-dev , Kishore Padmanabha , "jerinj@marvell.com" , Thomas Monjalon Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="00000000000059e4f805cd14f4a2" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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" --00000000000059e4f805cd14f4a2 Content-Type: text/plain; charset="UTF-8" On Tue, Sep 28, 2021 at 5:43 AM Ferruh Yigit wrote: > > 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? Correct. RTE_FLOW_ACTION_TYPE_SHARED is being used only for a range check. It is not really a supported action right now as far as the code is concerned. As of now, no document update is necessary. Thanks > If it is supported I can update the documentation. > > Thanks, > ferruh --00000000000059e4f805cd14f4a2--