From: Leon Romanovsky <leon@kernel.org>
To: Suman Ghosh <sumang@marvell.com>
Cc: sgoutham@marvell.com, gakula@marvell.com, sbhatta@marvell.com,
hkelam@marvell.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [net PATCH 3/3] octeontx2-af: Fix hash configuration for both source and destination IPv6
Date: Wed, 12 Jul 2023 15:39:23 +0300 [thread overview]
Message-ID: <20230712123923.GD41919@unreal> (raw)
In-Reply-To: <20230712111604.2290974-4-sumang@marvell.com>
On Wed, Jul 12, 2023 at 04:46:04PM +0530, Suman Ghosh wrote:
> As of today, hash reduction was supported only for source IPv6 address.
> This patch fixes that and adds supports for both source and
> destination IPv6 address.
>
> Fixes: a95ab93550d3 ("octeontx2-af: Use hashed field in MCAM key")
> Signed-off-by: Suman Ghosh <sumang@marvell.com>
> ---
> .../marvell/octeontx2/af/rvu_npc_hash.c | 37 +++++++++----------
> 1 file changed, 18 insertions(+), 19 deletions(-)
>
Thanks,
Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
next prev parent reply other threads:[~2023-07-12 12:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 11:16 [net PATCH 0/3] octeontx2-af: Fix issues with NPC field hash extract Suman Ghosh
2023-07-12 11:16 ` [net PATCH 1/3] octeontx2-af: Fix hash extraction mbox message Suman Ghosh
2023-07-12 12:39 ` Leon Romanovsky
2023-07-13 5:19 ` Jakub Kicinski
2023-07-14 7:06 ` [EXT] " Suman Ghosh
2023-07-12 11:16 ` [net PATCH 2/3] octeontx2-af: Fix hash extraction enable configuration Suman Ghosh
2023-07-12 12:39 ` Leon Romanovsky
2023-07-13 5:20 ` Jakub Kicinski
2023-07-14 7:07 ` [EXT] " Suman Ghosh
2023-07-12 11:16 ` [net PATCH 3/3] octeontx2-af: Fix hash configuration for both source and destination IPv6 Suman Ghosh
2023-07-12 12:39 ` Leon Romanovsky [this message]
2023-07-13 5:21 ` [net PATCH 0/3] octeontx2-af: Fix issues with NPC field hash extract Jakub Kicinski
2023-07-14 7:06 ` [EXT] " Suman Ghosh
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=20230712123923.GD41919@unreal \
--to=leon@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.com \
--cc=sumang@marvell.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.