From: Luca Boccassi <bluca@debian.org>
To: Kiran Kumar Kokkilagadda <kirankumark@marvell.com>,
Satheesh Paul <psatheesh@marvell.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [PATCH 20.11] net/octeontx2: fix flow MCAM priority management
Date: Wed, 16 Mar 2022 13:31:32 +0000 [thread overview]
Message-ID: <f2c965d6258d2cf28cae8be60cfc34c0304c2608.camel@debian.org> (raw)
In-Reply-To: <BYAPR18MB29657862C63E1309391E325AAC109@BYAPR18MB2965.namprd18.prod.outlook.com>
On Tue, 2022-03-15 at 15:47 +0000, Kiran Kumar Kokkilagadda wrote:
>
> > -----Original Message-----
> > From: psatheesh@marvell.com <psatheesh@marvell.com>
> > Sent: Tuesday, March 15, 2022 9:46 AM
> > To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>; Nithin Kumar Dabilpuram
> > <ndabilpuram@marvell.com>; Kiran Kumar Kokkilagadda
> > <kirankumark@marvell.com>
> > Cc: stable@dpdk.org; Satheesh Paul <psatheesh@marvell.com>
> > Subject: [PATCH 20.11] net/octeontx2: fix flow MCAM priority management
> >
> > 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>
>
> Acked-by: Kiran Kumar Kokkilagadda <kirankumark@marvell.com>
Thanks, applied and pushed.
--
Kind regards,
Luca Boccassi
prev parent reply other threads:[~2022-03-16 13:31 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 ` [EXT] " Satheesh Paul
2022-03-15 13:23 ` Luca Boccassi
2022-03-15 15:47 ` Kiran Kumar Kokkilagadda
2022-03-16 13:31 ` Luca Boccassi [this message]
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=f2c965d6258d2cf28cae8be60cfc34c0304c2608.camel@debian.org \
--to=bluca@debian.org \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=psatheesh@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).