From: patchwork-bot+netdevbpf@kernel.org
To: Corinna Vinschen <vinschen@redhat.com>
Cc: peppe.cavallaro@st.com, alexandre.torgue@foss.st.com,
joabreu@synopsys.com, netdev@vger.kernel.org
Subject: Re: [PATCH v2 net] net: stmmac: fix up RX flow hash indirection table when setting channels
Date: Tue, 04 Apr 2023 13:30:17 +0000 [thread overview]
Message-ID: <168061501781.4633.8487272906411516809.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230403121120.489138-1-vinschen@redhat.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 3 Apr 2023 14:11:20 +0200 you wrote:
> stmmac_reinit_queues() fails to fix up the RX hash. Even if the number
> of channels gets restricted, the output of `ethtool -x' indicates that
> all RX queues are used:
>
> $ ethtool -l enp0s29f2
> Channel parameters for enp0s29f2:
> Pre-set maximums:
> RX: 8
> TX: 8
> Other: n/a
> Combined: n/a
> Current hardware settings:
> RX: 8
> TX: 8
> Other: n/a
> Combined: n/a
> $ ethtool -x enp0s29f2
> RX flow hash indirection table for enp0s29f2 with 8 RX ring(s):
> 0: 0 1 2 3 4 5 6 7
> 8: 0 1 2 3 4 5 6 7
> [...]
> $ ethtool -L enp0s29f2 rx 3
> $ ethtool -x enp0s29f2
> RX flow hash indirection table for enp0s29f2 with 3 RX ring(s):
> 0: 0 1 2 3 4 5 6 7
> 8: 0 1 2 3 4 5 6 7
> [...]
>
> [...]
Here is the summary with links:
- [v2,net] net: stmmac: fix up RX flow hash indirection table when setting channels
https://git.kernel.org/netdev/net/c/218c597325f4
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-04-04 13:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 9:23 [PATCH net] net: stmmac: fix up RX flow hash indirection table when setting channels Corinna Vinschen
2023-04-01 4:46 ` Jakub Kicinski
2023-04-03 12:11 ` [PATCH v2 " Corinna Vinschen
2023-04-04 13:30 ` 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=168061501781.4633.8487272906411516809.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=joabreu@synopsys.com \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=vinschen@redhat.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.