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 V2 0/3] octeontx2-af: Fix issues with NPC field hash extract
Date: Tue, 18 Jul 2023 13:38:26 -0700 [thread overview]
Message-ID: <20230718133826.09db812c@kernel.org> (raw)
In-Reply-To: <20230714071141.2428144-1-sumang@marvell.com>
On Fri, 14 Jul 2023 12:41:38 +0530 Suman Ghosh wrote:
> This patchset fixes the issues with NPC field hash extract. This feature is
> supported only for CN10KB variant of CN10K series of silicons. This features
> helps to hash reduce 128 bit IPv6 source/destination address to 32 bit(also
> configurable) which can save 96 bit and can be used to store other key information
> during packet filtering.
For better or worse these patches seem to have already been merged
in May. Why are you resending this?
prev parent reply other threads:[~2023-07-18 20:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 7:11 [net PATCH V2 0/3] octeontx2-af: Fix issues with NPC field hash extract Suman Ghosh
2023-07-14 7:11 ` [net PATCH V2 1/3] octeontx2-af: Fix hash extraction mbox message Suman Ghosh
2023-07-14 7:11 ` [net PATCH V2 2/3] octeontx2-af: Fix hash extraction enable configuration Suman Ghosh
2023-07-14 7:11 ` [net PATCH V2 3/3] octeontx2-af: Fix hash configuration for both source and destination IPv6 Suman Ghosh
2023-07-18 20:38 ` Jakub Kicinski [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=20230718133826.09db812c@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).