From: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
To: Nelson Escobar <neescoba@cisco.com>
Cc: Christian Benvenuti <benve@cisco.com>,
Satish Kharat <satishkh@cisco.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
John Daley <johndale@cisco.com>
Subject: Re: [PATCH net-next] net/enic: Allow at least 8 RQs to always be used
Date: Wed, 21 May 2025 08:25:51 +0200 [thread overview]
Message-ID: <aC1x74D+eYJtvHQi@mev-dev.igk.intel.com> (raw)
In-Reply-To: <20250521-enic_min_8rq-v1-1-691bd2353273@cisco.com>
On Wed, May 21, 2025 at 01:19:29AM +0000, Nelson Escobar wrote:
> Enic started using netif_get_num_default_rss_queues() to set the number
> of RQs used in commit cc94d6c4d40c ("enic: Adjust used MSI-X
> wq/rq/cq/interrupt resources in a more robust way")
>
> This resulted in machines with less than 16 cpus using less than 8 RQs.
> Allow enic to use at least 8 RQs no matter how many cpus are in the
> machine to not impact existing enic workloads after a kernel upgrade.
>
> Reviewed-by: John Daley <johndale@cisco.com>
> Reviewed-by: Satish Kharat <satishkh@cisco.com>
> Signed-off-by: Nelson Escobar <neescoba@cisco.com>
> ---
> drivers/net/ethernet/cisco/enic/enic.h | 1 +
> drivers/net/ethernet/cisco/enic/enic_main.c | 3 ++-
> 2 files changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/cisco/enic/enic.h b/drivers/net/ethernet/cisco/enic/enic.h
> index 9c12e967e9f1299e1cf3e280a16fb9bf93ac607b..301b3f3114afa8f60c34c05661ee3cf67d4d6808 100644
> --- a/drivers/net/ethernet/cisco/enic/enic.h
> +++ b/drivers/net/ethernet/cisco/enic/enic.h
> @@ -26,6 +26,7 @@
>
> #define ENIC_WQ_MAX 256
> #define ENIC_RQ_MAX 256
> +#define ENIC_RQ_MIN_DEFAULT 8
>
> #define ENIC_WQ_NAPI_BUDGET 256
>
> diff --git a/drivers/net/ethernet/cisco/enic/enic_main.c b/drivers/net/ethernet/cisco/enic/enic_main.c
> index c753c35b26ebd12c500f2056b3eb583de8c6b076..6ef8a0d90bce38781d931f62518cf9bafb223288 100644
> --- a/drivers/net/ethernet/cisco/enic/enic_main.c
> +++ b/drivers/net/ethernet/cisco/enic/enic_main.c
> @@ -2296,7 +2296,8 @@ static int enic_adjust_resources(struct enic *enic)
> * used based on which resource is the most constrained
> */
> wq_avail = min(enic->wq_avail, ENIC_WQ_MAX);
> - rq_default = netif_get_num_default_rss_queues();
> + rq_default = max(netif_get_num_default_rss_queues(),
> + ENIC_RQ_MIN_DEFAULT);
> rq_avail = min3(enic->rq_avail, ENIC_RQ_MAX, rq_default);
> max_queues = min(enic->cq_avail,
> enic->intr_avail - ENIC_MSIX_RESERVED_INTR);
>
> ---
> base-commit: ae605349e1fa5a29cdeecf52f92aa76850900d90
> change-id: 20250513-enic_min_8rq-421f23897dc2
>
> Best regards,
Reviewed-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
> --
> Nelson Escobar <neescoba@cisco.com>
next prev parent reply other threads:[~2025-05-21 6:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 1:19 [PATCH net-next] net/enic: Allow at least 8 RQs to always be used Nelson Escobar
2025-05-21 6:25 ` Michal Swiatkowski [this message]
2025-05-22 3:50 ` patchwork-bot+netdevbpf
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=aC1x74D+eYJtvHQi@mev-dev.igk.intel.com \
--to=michal.swiatkowski@linux.intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=benve@cisco.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--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).