From: patchwork-bot+netdevbpf@kernel.org
To: Saeed Mahameed <saeed@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, saeedm@nvidia.com, netdev@vger.kernel.org,
tariqt@nvidia.com, msanalla@nvidia.com, shayd@nvidia.com,
moshe@nvidia.com
Subject: Re: [net-next 01/15] net/mlx5: Track the current number of completion EQs
Date: Tue, 08 Aug 2023 23:40:27 +0000 [thread overview]
Message-ID: <169153802718.28457.2520043547071157048.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230807175642.20834-2-saeed@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Saeed Mahameed <saeedm@nvidia.com>:
On Mon, 7 Aug 2023 10:56:28 -0700 you wrote:
> From: Maher Sanalla <msanalla@nvidia.com>
>
> In preparation to allocate completion EQs, add a counter to track the
> number of completion EQs currently allocated. Store the maximum number
> of EQs in max_comp_eqs variable.
>
> Signed-off-by: Maher Sanalla <msanalla@nvidia.com>
> Reviewed-by: Shay Drory <shayd@nvidia.com>
> Reviewed-by: Moshe Shemesh <moshe@nvidia.com>
> Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
>
> [...]
Here is the summary with links:
- [net-next,01/15] net/mlx5: Track the current number of completion EQs
https://git.kernel.org/netdev/net-next/c/18cf3d31f829
- [net-next,02/15] net/mlx5: Refactor completion IRQ request/release API
https://git.kernel.org/netdev/net-next/c/a1772de78d73
- [net-next,03/15] net/mlx5: Use xarray to store and manage completion IRQs
https://git.kernel.org/netdev/net-next/c/c8a0245c3937
- [net-next,04/15] net/mlx5: Refactor completion IRQ request/release handlers in EQ layer
https://git.kernel.org/netdev/net-next/c/54b2cf41b853
- [net-next,05/15] net/mlx5: Use xarray to store and manage completion EQs
https://git.kernel.org/netdev/net-next/c/273c697fdedc
- [net-next,06/15] net/mlx5: Implement single completion EQ create/destroy methods
https://git.kernel.org/netdev/net-next/c/e3e56775e913
- [net-next,07/15] net/mlx5: Introduce mlx5_cpumask_default_spread
https://git.kernel.org/netdev/net-next/c/ddd2c79da020
- [net-next,08/15] net/mlx5: Add IRQ vector to CPU lookup function
https://git.kernel.org/netdev/net-next/c/f3147015fa07
- [net-next,09/15] net/mlx5: Rename mlx5_comp_vectors_count() to mlx5_comp_vectors_max()
https://git.kernel.org/netdev/net-next/c/674dd4e2e04e
- [net-next,10/15] net/mlx5: Handle SF IRQ request in the absence of SF IRQ pool
https://git.kernel.org/netdev/net-next/c/54c5297801f3
- [net-next,11/15] net/mlx5: Allocate completion EQs dynamically
https://git.kernel.org/netdev/net-next/c/f14c1a14e632
- [net-next,12/15] net/mlx5: remove many unnecessary NULL values
https://git.kernel.org/netdev/net-next/c/a0ae00e71e3e
- [net-next,13/15] net/mlx5: Fix typo reminder -> remainder
https://git.kernel.org/netdev/net-next/c/58f6d9d04489
- [net-next,14/15] net/mlx5: E-Switch, Remove redundant arg ignore_flow_lvl
https://git.kernel.org/netdev/net-next/c/d602be220cf9
- [net-next,15/15] net/mlx5: Bridge, Only handle registered netdev bridge events
https://git.kernel.org/netdev/net-next/c/b56fb19c3379
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-08-08 23:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 17:56 [pull request][net-next 00/15] mlx5 updates 2023-08-07 Saeed Mahameed
2023-08-07 17:56 ` [net-next 01/15] net/mlx5: Track the current number of completion EQs Saeed Mahameed
2023-08-08 23:40 ` patchwork-bot+netdevbpf [this message]
2023-08-07 17:56 ` [net-next 02/15] net/mlx5: Refactor completion IRQ request/release API Saeed Mahameed
2023-08-07 17:56 ` [net-next 03/15] net/mlx5: Use xarray to store and manage completion IRQs Saeed Mahameed
2023-08-07 17:56 ` [net-next 04/15] net/mlx5: Refactor completion IRQ request/release handlers in EQ layer Saeed Mahameed
2023-08-07 17:56 ` [net-next 05/15] net/mlx5: Use xarray to store and manage completion EQs Saeed Mahameed
2023-08-07 17:56 ` [net-next 06/15] net/mlx5: Implement single completion EQ create/destroy methods Saeed Mahameed
2023-08-07 17:56 ` [net-next 07/15] net/mlx5: Introduce mlx5_cpumask_default_spread Saeed Mahameed
2023-08-07 17:56 ` [net-next 08/15] net/mlx5: Add IRQ vector to CPU lookup function Saeed Mahameed
2023-08-07 17:56 ` [net-next 09/15] net/mlx5: Rename mlx5_comp_vectors_count() to mlx5_comp_vectors_max() Saeed Mahameed
2023-08-07 17:56 ` [net-next 10/15] net/mlx5: Handle SF IRQ request in the absence of SF IRQ pool Saeed Mahameed
2023-08-07 17:56 ` [net-next 11/15] net/mlx5: Allocate completion EQs dynamically Saeed Mahameed
2023-08-07 17:56 ` [net-next 12/15] net/mlx5: remove many unnecessary NULL values Saeed Mahameed
2023-08-07 17:56 ` [net-next 13/15] net/mlx5: Fix typo reminder -> remainder Saeed Mahameed
2023-08-07 17:56 ` [net-next 14/15] net/mlx5: E-Switch, Remove redundant arg ignore_flow_lvl Saeed Mahameed
2023-08-07 17:56 ` [net-next 15/15] net/mlx5: Bridge, Only handle registered netdev bridge events Saeed Mahameed
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=169153802718.28457.2520043547071157048.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=moshe@nvidia.com \
--cc=msanalla@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeed@kernel.org \
--cc=saeedm@nvidia.com \
--cc=shayd@nvidia.com \
--cc=tariqt@nvidia.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).