patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Satheesh Paul <psatheesh@marvell.com>
To: Luca Boccassi <bluca@debian.org>,
	Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>,
	Kiran Kumar Kokkilagadda <kirankumark@marvell.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [EXT] Re: [PATCH 20.11] net/octeontx2: fix flow MCAM priority management
Date: Tue, 15 Mar 2022 12:46:57 +0000	[thread overview]
Message-ID: <DM5PR18MB224520630D70AA7AE5D02FA1BD109@DM5PR18MB2245.namprd18.prod.outlook.com> (raw)
In-Reply-To: <17d5a2164e217f962faf6d36619be8877d64ae53.camel@debian.org>

Hi,

Yes, the issue is specific to 20.11. On main branch this part of the code has been fully rewritten. (1f66919817 common/cnxk: improve MCAM entries management).
This is now backported with this patch to address the issue.

Thanks,
Satheesh. 

-----Original Message-----
From: Luca Boccassi <bluca@debian.org> 
Sent: 15 March 2022 05:14 PM
To: Satheesh Paul <psatheesh@marvell.com>; Jerin Jacob Kollanukkaran <jerinj@marvell.com>; Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>; Kiran Kumar Kokkilagadda <kirankumark@marvell.com>
Cc: stable@dpdk.org
Subject: [EXT] Re: [PATCH 20.11] net/octeontx2: fix flow MCAM priority management

External Email

----------------------------------------------------------------------
On Tue, 2022-03-15 at 09:46 +0530, psatheesh@marvell.com wrote:
> From: Satheesh Paul <psatheesh@marvell.com>
> 
> 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.
> 
> Fixes: 29a2017c70 ("net/octeontx2: add flow mbox utility functions")
> 
> Signed-off-by: Satheesh Paul <psatheesh@marvell.com>
> ---
>  drivers/net/octeontx2/otx2_flow.c       | 145 +----
>  drivers/net/octeontx2/otx2_flow.h       |  33 +-
>  drivers/net/octeontx2/otx2_flow_utils.c | 717 
> ++++++++++++------------
>  3 files changed, 405 insertions(+), 490 deletions(-)

Hi,

I don't see this patch on main - is it a bug specific to 20.11?

--
Kind regards,
Luca Boccassi

  reply	other threads:[~2022-03-15 12:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-15  4:16 psatheesh
2022-03-15 11:44 ` Luca Boccassi
2022-03-15 12:46   ` Satheesh Paul [this message]
2022-03-15 13:23     ` [EXT] " Luca Boccassi
2022-03-15 15:47 ` Kiran Kumar Kokkilagadda
2022-03-16 13:31   ` Luca Boccassi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DM5PR18MB224520630D70AA7AE5D02FA1BD109@DM5PR18MB2245.namprd18.prod.outlook.com \
    --to=psatheesh@marvell.com \
    --cc=bluca@debian.org \
    --cc=jerinj@marvell.com \
    --cc=kirankumark@marvell.com \
    --cc=ndabilpuram@marvell.com \
    --cc=stable@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).