From: patchwork-bot+netdevbpf@kernel.org
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, netdev@vger.kernel.org,
michal.swiatkowski@linux.intel.com
Subject: Re: [PATCH net-next 0/8][pull request] ice: use less resources in switchdev
Date: Fri, 29 Mar 2024 06:00:32 +0000 [thread overview]
Message-ID: <171169203267.14797.9683393618849219656.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240325202623.1012287-1-anthony.l.nguyen@intel.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Tony Nguyen <anthony.l.nguyen@intel.com>:
On Mon, 25 Mar 2024 13:26:08 -0700 you wrote:
> Michal Swiatkowski says:
>
> Switchdev is using one queue per created port representor. This can
> quickly lead to Rx queue shortage, as with subfunction support user
> can create high number of PRs.
>
> Save one MSI-X and 'number of PRs' * 1 queues.
> Refactor switchdev slow-path to use less resources (even no additional
> resources). Do this by removing control plane VSI and move its
> functionality to PF VSI. Even with current solution PF is acting like
> uplink and can't be used simultaneously for other use cases (adding
> filters can break slow-path).
>
> [...]
Here is the summary with links:
- [net-next,1/8] ice: remove eswitch changing queues algorithm
https://git.kernel.org/netdev/net-next/c/8c67b7a914cc
- [net-next,2/8] ice: do Tx through PF netdev in slow-path
https://git.kernel.org/netdev/net-next/c/defd52455aee
- [net-next,3/8] ice: default Tx rule instead of to queue
https://git.kernel.org/netdev/net-next/c/50d62022f455
- [net-next,4/8] ice: control default Tx rule in lag
https://git.kernel.org/netdev/net-next/c/9cba6e1767bf
- [net-next,5/8] ice: remove switchdev control plane VSI
https://git.kernel.org/netdev/net-next/c/33bf1e86231d
- [net-next,6/8] ice: change repr::id values
https://git.kernel.org/netdev/net-next/c/6235cb6e5b0d
- [net-next,7/8] ice: do switchdev slow-path Rx using PF VSI
https://git.kernel.org/netdev/net-next/c/44ba608db509
- [net-next,8/8] ice: count representor stats
https://git.kernel.org/netdev/net-next/c/4498159a5093
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:[~2024-03-29 6:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 20:26 [PATCH net-next 0/8][pull request] ice: use less resources in switchdev Tony Nguyen
2024-03-25 20:26 ` [PATCH net-next 1/8] ice: remove eswitch changing queues algorithm Tony Nguyen
2024-03-25 20:26 ` [PATCH net-next 2/8] ice: do Tx through PF netdev in slow-path Tony Nguyen
2024-03-25 20:26 ` [PATCH net-next 3/8] ice: default Tx rule instead of to queue Tony Nguyen
2024-03-25 20:26 ` [PATCH net-next 4/8] ice: control default Tx rule in lag Tony Nguyen
2024-03-25 20:26 ` [PATCH net-next 5/8] ice: remove switchdev control plane VSI Tony Nguyen
2024-03-25 20:26 ` [PATCH net-next 6/8] ice: change repr::id values Tony Nguyen
2024-03-25 20:26 ` [PATCH net-next 7/8] ice: do switchdev slow-path Rx using PF VSI Tony Nguyen
2024-03-25 20:26 ` [PATCH net-next 8/8] ice: count representor stats Tony Nguyen
2024-03-29 6:00 ` 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=171169203267.14797.9683393618849219656.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=michal.swiatkowski@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@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.