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 CE225A00BE for ; Tue, 15 Mar 2022 12:44:16 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9EB334014F; Tue, 15 Mar 2022 12:44:16 +0100 (CET) Received: from mail-ej1-f51.google.com (mail-ej1-f51.google.com [209.85.218.51]) by mails.dpdk.org (Postfix) with ESMTP id 92E6E4014F for ; Tue, 15 Mar 2022 12:44:15 +0100 (CET) Received: by mail-ej1-f51.google.com with SMTP id qa43so40374235ejc.12 for ; Tue, 15 Mar 2022 04:44:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:content-transfer-encoding:user-agent:mime-version; bh=xKy/829Pu6eAmT0XZasiBdNzffs9MmSDHTEYy486GNA=; b=IkZIK+Rn80NHPp5rt4rxbcCZOgBL41Nomd+RfBIUXL192E18VcomcR/fcmvf+hiNj2 NMrMXDNeEXsY5q0ApjC4aM4wTi9C+vSd9+wwGuO1jmjnz7FEgBoN/7xlmXQT95TjZz2O pRo8qKNw8LWAIxtCQCJYgHoVV6KIVrs1wbsOEYwrnMF08AhDi0UXOLTlVNYH/cPCTJg2 h2UdKR+NFqesifPx+sRB047hk4J3n1sLlNe6C+Ivkksiv5MOTLpGIyohmkeKcc9omuvp 5JnND43lj6nr9niUm3HOcZnJgcDjEUeVdR7+lF1m5Gk2aWUzshijfpND8iq0a46Er+4s 6/NQ== X-Gm-Message-State: AOAM530qmGjVAZ3BmeTz4oGFbUgebulUpHiETz7gX2siDsOPbIunIoQ1 1VuRIW1KNc3H1fSu7Fn7UonclBBbtp0= X-Google-Smtp-Source: ABdhPJy/WWXHv9+3ptr6moxPvf5DZ4w0tuoDf9ifJ2JWBJCSOE8Pk2g+QP46yXnWySTwTsdwj2uBZg== X-Received: by 2002:a17:907:7f1c:b0:6db:5e0f:1ac3 with SMTP id qf28-20020a1709077f1c00b006db5e0f1ac3mr22308855ejc.358.1647344655122; Tue, 15 Mar 2022 04:44:15 -0700 (PDT) Received: from localhost ([2a01:4b00:f41a:3600:360b:9754:2e3a:c344]) by smtp.gmail.com with ESMTPSA id a22-20020a50ff16000000b00410d029ea5csm9324962edu.96.2022.03.15.04.44.14 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 15 Mar 2022 04:44:14 -0700 (PDT) Message-ID: <17d5a2164e217f962faf6d36619be8877d64ae53.camel@debian.org> Subject: Re: [PATCH 20.11] net/octeontx2: fix flow MCAM priority management From: Luca Boccassi To: psatheesh@marvell.com, Jerin Jacob , Nithin Dabilpuram , Kiran Kumar K Cc: stable@dpdk.org Date: Tue, 15 Mar 2022 11:44:13 +0000 In-Reply-To: <20220315041620.2118828-1-psatheesh@marvell.com> References: <20220315041620.2118828-1-psatheesh@marvell.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.38.3-1+plugin MIME-Version: 1.0 X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org On Tue, 2022-03-15 at 09:46 +0530, psatheesh@marvell.com wrote: > From: Satheesh Paul >=20 > This patch fixes issues in rearranging the MCAM entries > when user is creating flows with priority levels. > The MCAM preallocation scheme and the free entry cache are > removed. For every flow created, an MCAM allocation request > is made to the kernel. Each priority level has a list of > MCAM entries. For every flow rule added, the MCAM entry > obtained from kernel is checked if it is at the correct user > specified priority. If not, the existing rules are moved > across MCAM entries so that the user specified priority is > maintained. >=20 > Fixes: 29a2017c70 ("net/octeontx2: add flow mbox utility functions") >=20 > Signed-off-by: Satheesh Paul > --- > =C2=A0drivers/net/octeontx2/otx2_flow.c | 145 +---- > =C2=A0drivers/net/octeontx2/otx2_flow.h | 33 +- > =C2=A0drivers/net/octeontx2/otx2_flow_utils.c | 717 ++++++++++++---------= --- > =C2=A03 files changed, 405 insertions(+), 490 deletions(-) Hi, I don't see this patch on main - is it a bug specific to 20.11? --=20 Kind regards, Luca Boccassi