From: Jakub Kicinski <kuba@kernel.org>
To: Dan Jurgens <danielj@nvidia.com>
Cc: Tariq Toukan <tariqt@nvidia.com>,
"David S. Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Saeed Mahameed <saeedm@nvidia.com>, Gal Pressman <gal@nvidia.com>,
Leon Romanovsky <leonro@nvidia.com>, William Tu <witu@nvidia.com>
Subject: Re: [PATCH net-next V2 01/10] net/mlx5: IFC updates for SF max IO EQs
Date: Wed, 10 Jul 2024 17:44:01 -0700 [thread overview]
Message-ID: <20240710174401.70e8f956@kernel.org> (raw)
In-Reply-To: <CH0PR12MB858029A605D7AF3849C54F6AC9A42@CH0PR12MB8580.namprd12.prod.outlook.com>
On Wed, 10 Jul 2024 13:08:31 +0000 Dan Jurgens wrote:
> > > Expose a new cap sf_eq_usage. The vhca_resource_manager can write this
> > > cap, indicating the SF driver should use max_num_eqs_24b to determine
> > > how many EQs to use.
> >
> > How does vhca_resource_manager write this cap?
>
> In most literal sense, MLX5_SET(cmd_hca_cap_2, hca_caps, sf_eq_usage, 1);.
>
> But getting there flows through:
> devlink port function set pci/0000:08:00.0/32768 max_io_eqs 32
Makes sense, include in the commit message, please?
next prev parent reply other threads:[~2024-07-11 0:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 8:00 [PATCH net-next V2 00/10] mlx5 misc patches 2023-07-08 Tariq Toukan
2024-07-08 8:00 ` [PATCH net-next V2 01/10] net/mlx5: IFC updates for SF max IO EQs Tariq Toukan
2024-07-10 1:54 ` Jakub Kicinski
2024-07-10 13:08 ` Dan Jurgens
2024-07-11 0:44 ` Jakub Kicinski [this message]
2024-07-08 8:00 ` [PATCH net-next V2 02/10] net/mlx5: Set sf_eq_usage for SF max EQs Tariq Toukan
2024-07-08 8:00 ` [PATCH net-next V2 03/10] net/mlx5: Set default max eqs for SFs Tariq Toukan
2024-07-08 8:00 ` [PATCH net-next V2 04/10] net/mlx5: Use set number of max EQs Tariq Toukan
2024-07-08 8:00 ` [PATCH net-next V2 05/10] net/mlx5: Add support for MTPTM and MTCTR registers Tariq Toukan
2024-07-08 8:00 ` [PATCH net-next V2 06/10] net/mlx5: Add support for enabling PTM PCI capability Tariq Toukan
2024-07-08 8:00 ` [PATCH net-next V2 07/10] net/mlx5: Implement PTM cross timestamping support Tariq Toukan
2024-07-10 1:58 ` Jakub Kicinski
2024-07-08 8:00 ` [PATCH net-next V2 08/10] net/mlx5: DR, Remove definer functions from SW Steering API Tariq Toukan
2024-07-08 8:00 ` [PATCH net-next V2 09/10] net/mlx5e: SHAMPO, Add missing aggregate counter Tariq Toukan
2024-07-08 8:00 ` [PATCH net-next V2 10/10] net/mlx5e: CT: Initialize err to 0 to avoid warning Tariq Toukan
2024-07-08 10:58 ` [PATCH net-next V2 00/10] mlx5 misc patches 2023-07-08 Simon Horman
2024-07-08 12:17 ` Tariq Toukan
2024-07-10 2:10 ` 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=20240710174401.70e8f956@kernel.org \
--to=kuba@kernel.org \
--cc=danielj@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=leonro@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.com \
--cc=witu@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 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).