From: patchwork-bot+netdevbpf@kernel•org
To: Saeed Mahameed <saeed@kernel•org>
Cc: davem@davemloft•net, kuba@kernel•org, netdev@vger•kernel.org,
tariqt@nvidia•com, maximmi@nvidia•com, saeedm@nvidia•com
Subject: Re: [net-next 01/16] net/mlx5e: Prohibit inner indir TIRs in IPoIB
Date: Mon, 26 Jul 2021 21:40:09 +0000 [thread overview]
Message-ID: <162733560955.28049.12550604033505103215.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210726165544.389143-2-saeed@kernel.org>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Mon, 26 Jul 2021 09:55:29 -0700 you wrote:
> From: Maxim Mikityanskiy <maximmi@nvidia•com>
>
> TIR's rx_hash_field_selector_inner can be enabled only when
> tunneled_offload_en = 1. tunneled_offload_en is filled according to the
> tunneled_offload_en field in struct mlx5e_params, which is false in the
> IPoIB profile. On the other hand, the IPoIB profile passes inner_ttc =
> true to mlx5e_create_indirect_tirs, which potentially allows the latter
> function to attempt to create inner indirect TIRs without having
> tunneled_offload_en set.
>
> [...]
Here is the summary with links:
- [net-next,01/16] net/mlx5e: Prohibit inner indir TIRs in IPoIB
https://git.kernel.org/netdev/net-next/c/9c43f3865c2a
- [net-next,02/16] net/mlx5e: Block LRO if firmware asks for tunneled LRO
https://git.kernel.org/netdev/net-next/c/26ab7b384525
- [net-next,03/16] net/mlx5: Take TIR destruction out of the TIR list lock
https://git.kernel.org/netdev/net-next/c/69994ef3da66
- [net-next,04/16] net/mlx5e: Check if inner FT is supported outside of create/destroy functions
https://git.kernel.org/netdev/net-next/c/bc5506a166c3
- [net-next,05/16] net/mlx5e: Convert RQT to a dedicated object
https://git.kernel.org/netdev/net-next/c/06e9f13ac5cc
- [net-next,06/16] net/mlx5e: Move mlx5e_build_rss_params() call to init_rx
https://git.kernel.org/netdev/net-next/c/4ad31849771a
- [net-next,07/16] net/mlx5e: Move RX resources to a separate struct
https://git.kernel.org/netdev/net-next/c/3f22d6c77bb9
- [net-next,08/16] net/mlx5e: Take RQT out of TIR and group RX resources
https://git.kernel.org/netdev/net-next/c/0570c1c95817
- [net-next,09/16] net/mlx5e: Use mlx5e_rqt_get_rqtn to access RQT hardware id
https://git.kernel.org/netdev/net-next/c/093d4bc1731d
- [net-next,10/16] net/mlx5e: Remove mlx5e_priv usage from mlx5e_build_*tir_ctx*()
https://git.kernel.org/netdev/net-next/c/983c9da2b1e1
- [net-next,11/16] net/mlx5e: Remove lro_param from mlx5e_build_indir_tir_ctx_common()
https://git.kernel.org/netdev/net-next/c/a402e3a7470d
- [net-next,12/16] net/mlx5e: Remove mdev from mlx5e_build_indir_tir_ctx_common()
https://git.kernel.org/netdev/net-next/c/4b3e42eecb1c
- [net-next,13/16] net/mlx5e: Create struct mlx5e_rss_params_hash
https://git.kernel.org/netdev/net-next/c/6fe5ff2c7780
- [net-next,14/16] net/mlx5e: Convert TIR to a dedicated object
https://git.kernel.org/netdev/net-next/c/a6696735d694
- [net-next,15/16] net/mlx5e: Move management of indir traffic types to rx_res
https://git.kernel.org/netdev/net-next/c/65d6b6e5a5da
- [net-next,16/16] net/mlx5e: Use the new TIR API for kTLS
https://git.kernel.org/netdev/net-next/c/09f83569189f
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:[~2021-07-26 21:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 16:55 [pull request][net-next 00/16] mlx5 updates 2021-07-24 Saeed Mahameed
2021-07-26 16:55 ` [net-next 01/16] net/mlx5e: Prohibit inner indir TIRs in IPoIB Saeed Mahameed
2021-07-26 21:40 ` patchwork-bot+netdevbpf [this message]
2021-07-26 16:55 ` [net-next 02/16] net/mlx5e: Block LRO if firmware asks for tunneled LRO Saeed Mahameed
2021-07-26 16:55 ` [net-next 03/16] net/mlx5: Take TIR destruction out of the TIR list lock Saeed Mahameed
2021-07-26 16:55 ` [net-next 04/16] net/mlx5e: Check if inner FT is supported outside of create/destroy functions Saeed Mahameed
2021-07-26 16:55 ` [net-next 05/16] net/mlx5e: Convert RQT to a dedicated object Saeed Mahameed
2021-07-26 16:55 ` [net-next 06/16] net/mlx5e: Move mlx5e_build_rss_params() call to init_rx Saeed Mahameed
2021-07-26 16:55 ` [net-next 07/16] net/mlx5e: Move RX resources to a separate struct Saeed Mahameed
2021-07-26 16:55 ` [net-next 08/16] net/mlx5e: Take RQT out of TIR and group RX resources Saeed Mahameed
2021-07-26 16:55 ` [net-next 09/16] net/mlx5e: Use mlx5e_rqt_get_rqtn to access RQT hardware id Saeed Mahameed
2021-07-26 16:55 ` [net-next 10/16] net/mlx5e: Remove mlx5e_priv usage from mlx5e_build_*tir_ctx*() Saeed Mahameed
2021-07-26 16:55 ` [net-next 11/16] net/mlx5e: Remove lro_param from mlx5e_build_indir_tir_ctx_common() Saeed Mahameed
2021-07-26 16:55 ` [net-next 12/16] net/mlx5e: Remove mdev " Saeed Mahameed
2021-07-26 16:55 ` [net-next 13/16] net/mlx5e: Create struct mlx5e_rss_params_hash Saeed Mahameed
2021-07-26 16:55 ` [net-next 14/16] net/mlx5e: Convert TIR to a dedicated object Saeed Mahameed
2021-07-26 16:55 ` [net-next 15/16] net/mlx5e: Move management of indir traffic types to rx_res Saeed Mahameed
2021-07-26 16:55 ` [net-next 16/16] net/mlx5e: Use the new TIR API for kTLS 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=162733560955.28049.12550604033505103215.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=kuba@kernel$(echo .)org \
--cc=maximmi@nvidia$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=saeed@kernel$(echo .)org \
--cc=saeedm@nvidia$(echo .)com \
--cc=tariqt@nvidia$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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