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 AD00441B5D; Tue, 29 Aug 2023 09:38:36 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 860F940279; Tue, 29 Aug 2023 09:38:36 +0200 (CEST) Received: from mail-vk1-f178.google.com (mail-vk1-f178.google.com [209.85.221.178]) by mails.dpdk.org (Postfix) with ESMTP id 928594026A; Tue, 29 Aug 2023 09:38:34 +0200 (CEST) Received: by mail-vk1-f178.google.com with SMTP id 71dfb90a1353d-49040dc5cedso526923e0c.3; Tue, 29 Aug 2023 00:38:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1693294714; x=1693899514; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=h3l+5jrMoBi51QGrjdRATV19G2b0ddnlkCRR+LVyNaM=; b=jT7dnk+TSGmqfnMj59sFTjvP7bXCsCvKGD7/jOlzrd++9+jjupP+iReoScYfy3kYnu +8LV3Lk5ksR7ZHbhK9yqiJknni8k4ndqCQS7fUmyQzOaGJypO+o0CP1vEDMSsnrz7DGJ QxlwGPB7r+3bvGkfgySINE7LAzJHsLdJJ94T918jYWPtrZw67dd5LzMT2xQLZ5TTNRA6 hn11Q1nc0mq/Mz/8VOGYVUz5m87hc71xhZnyDYyDmv6EYJCaj0XAZGObDQ1Ln7m82xnt dlcGpz+zzvzG2HhK45PfFGKwgwI9kclu1Ly9CXL989voylWUcB6kXGFTzW0wZcWzX/3X m2BQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693294714; x=1693899514; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=h3l+5jrMoBi51QGrjdRATV19G2b0ddnlkCRR+LVyNaM=; b=axYprcAYTTNfSczzKU3pH1tWN34WYaUw4lLHm1lUaAoCBj2hTTFqTguprcUvlQQXOo i8FloxfSiMnVpP/yUy+J+qv7gUICDTSX635d9167jGc9mkUcDUHhg0c9JVSdvwMCKz5D oB5uu2R7ejT0OIqLZo6eCjtE2cdnafsQ/999i7nj0dGgpQ4nf/E+18yjgBN+SAokrY+3 AhIgC/DXL/HwgRUIarfgSPa4A/LD956vpfP3wVkS7vgSgpF7Vc8ut4bGq/LDuBU9ipEK 6B36zti1Sbh8NyWXYGruj02ixR3LsOvwa0MW41bdEFFgLj5UO7y47EVtfLCWS+xAj3J3 BWuQ== X-Gm-Message-State: AOJu0YwkfEKPse49353fEEHp+hFxpndQYHQY1dwcyBYPnvgQikmENXyP IVfHrehwXVEwqn0fDiI8+qIzl0mDg2YqfM/5rjk= X-Google-Smtp-Source: AGHT+IFPxGrq5QiQSl1vJHJSdFrMR7j4Bxa8HdiU6Iwsy6Gh0JzUiWyoO81UMRIYKthzY+Quo6MiHyUPzKsFIa65k5w= X-Received: by 2002:a05:6122:d0f:b0:490:393e:9053 with SMTP id az15-20020a0561220d0f00b00490393e9053mr3816951vkb.13.1693294713736; Tue, 29 Aug 2023 00:38:33 -0700 (PDT) MIME-Version: 1.0 References: <20230802173451.3151646-1-qi.z.zhang@intel.com> <98CBD80474FA8B44BF855DF32C47DC35D87AB8@smartserver.smartshare.dk> <98CBD80474FA8B44BF855DF32C47DC35D87AB9@smartserver.smartshare.dk> <98CBD80474FA8B44BF855DF32C47DC35D87ABF@smartserver.smartshare.dk> <98CBD80474FA8B44BF855DF32C47DC35D87AC2@smartserver.smartshare.dk> <98CBD80474FA8B44BF855DF32C47DC35D87AC4@smartserver.smartshare.dk> In-Reply-To: From: Jerin Jacob Date: Tue, 29 Aug 2023 13:08:07 +0530 Message-ID: Subject: Re: DPDK community: RTE_FLOW support for P4-programmable devices To: "Dumitrescu, Cristian" Cc: Ori Kam , =?UTF-8?Q?Morten_Br=C3=B8rup?= , "Zhang, Qi Z" , "NBU-Contact-Thomas Monjalon (EXTERNAL)" , "david.marchand@redhat.com" , "Richardson, Bruce" , "jerinj@marvell.com" , "ferruh.yigit@amd.com" , "techboard@dpdk.org" , "Mcnamara, John" , "Zhang, Helin" , "dev@dpdk.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 On Mon, Aug 28, 2023 at 9:43=E2=80=AFPM Dumitrescu, Cristian wrote: > > > > We just set up a community call for next week to discuss in more deta= ils the > > > proposal for RTE_FLOW extensions to support P4-programmable devices > > > https://mails.dpdk.org/archives/dev/2023-August/273703.html and look = for > > > ways to converge and make progress. > > > > > > All the people from To: and CC: are already invited. To avoid clutter= ing > > people's > > > calendars, I did not add dev@dpdk.org, so if anybody else wants to at= tend, > > > please send me a private email and I will be happy to forward the inv= ite. > > > > > > Thanks, > > > Cristian > > Attendees: Morten Brorup, Jerin Jacob, Anoob Joseph, Vipin Varghese, Qi Z= hang, > Cristian Dumitrescu > > 1. Ori (RTE_FLOW maintainer) and others were not present, probably on vac= ation, > hopefully they will be able to attend the next call on this topic. Ferruh= had a last > minute conflict that he could not avoid. > > 2. Cristian presented a few slides (attached) with the problem statement,= current > RTE_FLOW gaps for P4-programmable devices and the list of current solutio= n > proposals. > > 3. Everybody on the call agreed that the P4-programmable devices from Int= el, > AMD and others need to be fully supported by DPDK and that there are some > gaps in RTE_FLOW to be fixed for supporting these devices. Personally, It makes sense to me to have normative DPDK API to send p4 runtime message to the ethdev so that we have "vendor neutral + DPDK based" p4 runtime backend. I prefer to have specialized ethdev ops for this due to the following reaso= ns. # If the ethdev has both real TCAM based HW(for existing rte_flow patterns and actions) and SW agent to receive P4 runtime message etc. Typically, it needs to take a different path in driver to talk. Assume, if = you have cascaded patterns/actions, One is targeted for TCAM and other for SW agent for p4, one need to have serious amount checking for dispatching.It complicates the driver and forbid to have driver optimization especially cases for templates etc. if user making rules for both category of HW. # All we need "char buffer//string" based communication ethdev <-> app.