From: patchwork-bot+netdevbpf@kernel.org
To: Hariprasad Kelam <hkelam@marvell.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kuba@kernel.org, davem@davemloft.net, sgoutham@marvell.com,
gakula@marvell.com, jerinj@marvell.com, lcherian@marvell.com,
sbhatta@marvell.com, naveenm@marvell.com, edumazet@google.com,
pabeni@redhat.com
Subject: Re: [net 0/2] octeontx2: Fix issues with promisc/allmulti mode
Date: Mon, 11 Dec 2023 10:10:23 +0000 [thread overview]
Message-ID: <170228942361.26769.3231506778434195901.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231208065610.16086-1-hkelam@marvell.com>
Hello:
This series was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 8 Dec 2023 12:26:08 +0530 you wrote:
> When interface is configured in promisc/all multi mode, low network
> performance observed. This series patches address the same.
>
> Patch1: Change the promisc/all multi mcam entry action to unicast if
> there are no trusted vfs associated with PF.
>
> Patch2: Configures RSS flow algorithm in promisc/all multi mcam entries
> to address flow distribution issues.
>
> [...]
Here is the summary with links:
- [net,1/2] octeontx2-pf: Fix promisc mcam entry action
https://git.kernel.org/netdev/net/c/dbda436824de
- [net,2/2] octeontx2-af: Update RSS algorithm index
https://git.kernel.org/netdev/net/c/570ba37898ec
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-12-11 10:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 6:56 [net 0/2] octeontx2: Fix issues with promisc/allmulti mode Hariprasad Kelam
2023-12-08 6:56 ` [net 1/2] octeontx2-pf: Fix promisc mcam entry action Hariprasad Kelam
2023-12-08 6:56 ` [net 2/2] octeontx2-af: Update RSS algorithm index Hariprasad Kelam
2023-12-11 10:10 ` patchwork-bot+netdevbpf [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=170228942361.26769.3231506778434195901.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=jerinj@marvell.com \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=naveenm@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@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