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, kliteyn@nvidia.com, cmi@nvidia.com,
valex@nvidia.com
Subject: Re: [net-next V2 01/14] net/mlx5: DR, In destroy flow, free resources even if FW command failed
Date: Sat, 29 Oct 2022 06:30:21 +0000 [thread overview]
Message-ID: <166702502193.25217.18098583636278445187.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221027145643.6618-2-saeed@kernel.org>
Hello:
This series was applied to netdev/net-next.git (master)
by Saeed Mahameed <saeedm@nvidia.com>:
On Thu, 27 Oct 2022 15:56:30 +0100 you wrote:
> From: Yevgeny Kliteynik <kliteyn@nvidia.com>
>
> Otherwise resources will never be freed and refcount will not be decreased.
>
> Signed-off-by: Chris Mi <cmi@nvidia.com>
> Signed-off-by: Yevgeny Kliteynik <kliteyn@nvidia.com>
> Reviewed-by: Alex Vesker <valex@nvidia.com>
> Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
>
> [...]
Here is the summary with links:
- [net-next,V2,01/14] net/mlx5: DR, In destroy flow, free resources even if FW command failed
https://git.kernel.org/netdev/net-next/c/14335d54e721
- [net-next,V2,02/14] net/mlx5: DR, Fix the SMFS sync_steering for fast teardown
https://git.kernel.org/netdev/net-next/c/c4193a1281ac
- [net-next,V2,03/14] net/mlx5: DR, Check device state when polling CQ
https://git.kernel.org/netdev/net-next/c/5fd08f653991
- [net-next,V2,04/14] net/mlx5: DR, Remove unneeded argument from dr_icm_chunk_destroy
https://git.kernel.org/netdev/net-next/c/d277b55f0fa8
- [net-next,V2,05/14] net/mlx5: DR, For short chains of STEs, avoid allocating ste_arr dynamically
https://git.kernel.org/netdev/net-next/c/b9b81e1e9382
- [net-next,V2,06/14] net/mlx5: DR, Initialize chunk's ste_arrays at chunk creation
https://git.kernel.org/netdev/net-next/c/06ab4a4089d4
- [net-next,V2,07/14] net/mlx5: DR, Handle domain memory resources init/uninit separately
https://git.kernel.org/netdev/net-next/c/183a6706a07e
- [net-next,V2,08/14] net/mlx5: DR, In rehash write the line in the entry immediately
https://git.kernel.org/netdev/net-next/c/1bea2dc7f4ff
- [net-next,V2,09/14] net/mlx5: DR, Manage STE send info objects in pool
https://git.kernel.org/netdev/net-next/c/17b56073a066
- [net-next,V2,10/14] net/mlx5: DR, Allocate icm_chunks from their own slab allocator
https://git.kernel.org/netdev/net-next/c/fd785e5213f0
- [net-next,V2,11/14] net/mlx5: DR, Allocate htbl from its own slab allocator
https://git.kernel.org/netdev/net-next/c/fb628b71fb2a
- [net-next,V2,12/14] net/mlx5: DR, Lower sync threshold for ICM hot memory
https://git.kernel.org/netdev/net-next/c/133ea373a043
- [net-next,V2,13/14] net/mlx5: DR, Keep track of hot ICM chunks in an array instead of list
https://git.kernel.org/netdev/net-next/c/4519fc45beeb
- [net-next,V2,14/14] net/mlx5: DR, Remove the buddy used_list
https://git.kernel.org/netdev/net-next/c/edaea001442a
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:[~2022-10-29 6:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 14:56 [pull request][net-next V2 00/14] mlx5 updates 2022-10-24 Saeed Mahameed
2022-10-27 14:56 ` [net-next V2 01/14] net/mlx5: DR, In destroy flow, free resources even if FW command failed Saeed Mahameed
2022-10-29 6:30 ` patchwork-bot+netdevbpf [this message]
2022-10-27 14:56 ` [net-next V2 02/14] net/mlx5: DR, Fix the SMFS sync_steering for fast teardown Saeed Mahameed
2022-10-27 14:56 ` [net-next V2 03/14] net/mlx5: DR, Check device state when polling CQ Saeed Mahameed
2022-10-27 14:56 ` [net-next V2 04/14] net/mlx5: DR, Remove unneeded argument from dr_icm_chunk_destroy Saeed Mahameed
2022-10-27 14:56 ` [net-next V2 05/14] net/mlx5: DR, For short chains of STEs, avoid allocating ste_arr dynamically Saeed Mahameed
2022-10-27 14:56 ` [net-next V2 06/14] net/mlx5: DR, Initialize chunk's ste_arrays at chunk creation Saeed Mahameed
2022-10-27 14:56 ` [net-next V2 07/14] net/mlx5: DR, Handle domain memory resources init/uninit separately Saeed Mahameed
2022-10-27 14:56 ` [net-next V2 08/14] net/mlx5: DR, In rehash write the line in the entry immediately Saeed Mahameed
2022-10-27 14:56 ` [net-next V2 09/14] net/mlx5: DR, Manage STE send info objects in pool Saeed Mahameed
2022-10-27 14:56 ` [net-next V2 10/14] net/mlx5: DR, Allocate icm_chunks from their own slab allocator Saeed Mahameed
2022-10-27 14:56 ` [net-next V2 11/14] net/mlx5: DR, Allocate htbl from its " Saeed Mahameed
2022-10-27 14:56 ` [net-next V2 12/14] net/mlx5: DR, Lower sync threshold for ICM hot memory Saeed Mahameed
2022-10-27 14:56 ` [net-next V2 13/14] net/mlx5: DR, Keep track of hot ICM chunks in an array instead of list Saeed Mahameed
2022-10-27 14:56 ` [net-next V2 14/14] net/mlx5: DR, Remove the buddy used_list 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=166702502193.25217.18098583636278445187.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=cmi@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kliteyn@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeed@kernel.org \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.com \
--cc=valex@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 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.