From: patchwork-bot+netdevbpf@kernel.org
To: Nelson Escobar (neescoba) <neescoba@cisco.com>
Cc: johndale@cisco.com, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, benve@cisco.com, satishkh@cisco.com,
andrew+netdev@lunn.ch, davem@davemloft.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
horms@kernel.org
Subject: Re: [PATCH net-next v4 0/7] enic: Use all the resources configured on VIC
Date: Fri, 15 Nov 2024 23:50:30 +0000 [thread overview]
Message-ID: <173171463001.2772765.5468131384631362067.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241113-remove_vic_resource_limits-v4-0-a34cf8570c67@cisco.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 13 Nov 2024 23:56:32 +0000 you wrote:
> Allow users to configure and use more than 8 rx queues and 8 tx queues
> on the Cisco VIC.
>
> This series changes the maximum number of tx and rx queues supported
> from 8 to the hardware limit of 256, and allocates memory based on the
> number of resources configured on the VIC.
>
> [...]
Here is the summary with links:
- [net-next,v4,1/7] enic: Create enic_wq/rq structures to bundle per wq/rq data
https://git.kernel.org/netdev/net-next/c/b67609c93153
- [net-next,v4,2/7] enic: Make MSI-X I/O interrupts come after the other required ones
https://git.kernel.org/netdev/net-next/c/231646cb6a8c
- [net-next,v4,3/7] enic: Save resource counts we read from HW
https://git.kernel.org/netdev/net-next/c/5aee3324724a
- [net-next,v4,4/7] enic: Allocate arrays in enic struct based on VIC config
https://git.kernel.org/netdev/net-next/c/a64e5492ca90
- [net-next,v4,5/7] enic: Adjust used MSI-X wq/rq/cq/interrupt resources in a more robust way
https://git.kernel.org/netdev/net-next/c/cc94d6c4d40c
- [net-next,v4,6/7] enic: Move enic resource adjustments to separate function
https://git.kernel.org/netdev/net-next/c/374f6c04df8e
- [net-next,v4,7/7] enic: Move kdump check into enic_adjust_resources()
https://git.kernel.org/netdev/net-next/c/a28ccf1d6c10
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-11-15 23:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 23:56 [PATCH net-next v4 0/7] enic: Use all the resources configured on VIC Nelson Escobar
2024-11-13 23:56 ` [PATCH net-next v4 1/7] enic: Create enic_wq/rq structures to bundle per wq/rq data Nelson Escobar
2024-11-14 16:15 ` Vadim Fedorenko
2024-11-14 19:46 ` Nelson Escobar (neescoba)
2024-11-13 23:56 ` [PATCH net-next v4 2/7] enic: Make MSI-X I/O interrupts come after the other required ones Nelson Escobar
2024-11-14 16:22 ` Vadim Fedorenko
2024-11-13 23:56 ` [PATCH net-next v4 3/7] enic: Save resource counts we read from HW Nelson Escobar
2024-11-14 16:16 ` Vadim Fedorenko
2024-11-13 23:56 ` [PATCH net-next v4 4/7] enic: Allocate arrays in enic struct based on VIC config Nelson Escobar
2024-11-14 16:21 ` Vadim Fedorenko
2024-11-13 23:56 ` [PATCH net-next v4 5/7] enic: Adjust used MSI-X wq/rq/cq/interrupt resources in a more robust way Nelson Escobar
2024-11-14 16:29 ` Vadim Fedorenko
2024-11-13 23:56 ` [PATCH net-next v4 6/7] enic: Move enic resource adjustments to separate function Nelson Escobar
2024-11-14 16:31 ` Vadim Fedorenko
2024-11-13 23:56 ` [PATCH net-next v4 7/7] enic: Move kdump check into enic_adjust_resources() Nelson Escobar
2024-11-14 16:32 ` Vadim Fedorenko
2024-11-15 23:50 ` 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=173171463001.2772765.5468131384631362067.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=benve@cisco.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=johndale@cisco.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neescoba@cisco.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=satishkh@cisco.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).