From: Nelson Escobar via B4 Relay <devnull+neescoba.cisco.com@kernel.org>
To: John Daley <johndale@cisco.com>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
Christian Benvenuti <benve@cisco.com>,
Satish Kharat <satishkh@cisco.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Nelson Escobar <neescoba@cisco.com>,
Simon Horman <horms@kernel.org>
Subject: [PATCH net-next v2 0/5] enic: Use all the resources configured on VIC
Date: Thu, 24 Oct 2024 18:19:42 -0700 [thread overview]
Message-ID: <20241024-remove_vic_resource_limits-v2-0-039b8cae5fdd@cisco.com> (raw)
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.
Signed-off-by: Nelson Escobar <neescoba@cisco.com>
---
Changes in v2:
- Followed Kalesh's suggestions: removed redundant NULL assigments,
returning -ENOMEM directly
- Reviewed-by tag for Simon Horman <horms@kernel.org>
- Marked Satish Kharat and John Daley as co-developers to better reflect
their role in this patch set
- Link to v1: https://lore.kernel.org/r/20241022041707.27402-2-neescoba@cisco.com
---
Nelson Escobar (5):
enic: Create enic_wq/rq structures to bundle per wq/rq data
enic: Make MSI-X I/O interrupts come after the other required ones
enic: Save resource counts we read from HW
enic: Allocate arrays in enic struct based on VIC config
enic: Adjust used MSI-X wq/rq/cq/interrupt resources in a more robust way
drivers/net/ethernet/cisco/enic/enic.h | 62 ++--
drivers/net/ethernet/cisco/enic/enic_ethtool.c | 8 +-
drivers/net/ethernet/cisco/enic/enic_main.c | 397 +++++++++++++++----------
drivers/net/ethernet/cisco/enic/enic_res.c | 33 +-
4 files changed, 294 insertions(+), 206 deletions(-)
---
base-commit: 6f07cd8301706b661776074ddc97c991d107cc91
change-id: 20241023-remove_vic_resource_limits-eaa64f9e65fb
Best regards,
--
Nelson Escobar <neescoba@cisco.com>
next reply other threads:[~2024-10-25 1:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 1:19 Nelson Escobar via B4 Relay [this message]
2024-10-25 1:19 ` [PATCH net-next v2 1/5] enic: Create enic_wq/rq structures to bundle per wq/rq data Nelson Escobar via B4 Relay
2024-10-25 1:19 ` [PATCH net-next v2 2/5] enic: Make MSI-X I/O interrupts come after the other required ones Nelson Escobar via B4 Relay
2024-10-25 1:19 ` [PATCH net-next v2 3/5] enic: Save resource counts we read from HW Nelson Escobar via B4 Relay
2024-10-25 1:19 ` [PATCH net-next v2 4/5] enic: Allocate arrays in enic struct based on VIC config Nelson Escobar via B4 Relay
2024-10-25 1:19 ` [PATCH net-next v2 5/5] enic: Adjust used MSI-X wq/rq/cq/interrupt resources in a more robust way Nelson Escobar via B4 Relay
2024-11-01 1:19 ` Jakub Kicinski
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=20241024-remove_vic_resource_limits-v2-0-039b8cae5fdd@cisco.com \
--to=devnull+neescoba.cisco.com@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
all inboxes | Powered by JetHome®