From: Jakub Kicinski <kuba@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>, <pabeni@redhat.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [net PATCH 1/3] octeontx2-af: Fix hash extraction mbox message
Date: Wed, 12 Jul 2023 22:19:38 -0700 [thread overview]
Message-ID: <20230712221938.0ae4374e@kernel.org> (raw)
In-Reply-To: <20230712111604.2290974-2-sumang@marvell.com>
On Wed, 12 Jul 2023 16:46:02 +0530 Suman Ghosh wrote:
> As of today, hash extraction mbox message response supports only the
> secret key. This patch adds support to extract both hash mask and hash
> control along with the secret key. These are needed to use hash
> reduction of 128 bit IPv6 address to 32 bit.
What are hash mask and hash control?
Why is this a fix and not a new feature / extension?
next prev parent reply other threads:[~2023-07-13 5:19 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 [this message]
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
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=20230712221938.0ae4374e@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--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 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).