public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Parav Pandit <parav@nvidia.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, corbet@lwn.net,
	dw@davidwei.uk, kalesh-anakkur.purayil@broadcom.com,
	saeedm@nvidia.com, leon@kernel.org, shayd@nvidia.com,
	danielj@nvidia.com, dchumak@nvidia.com,
	linux-doc@vger.kernel.org, linux-rdma@vger.kernel.org
Subject: Re: [net-next v4 2/2] mlx5/core: Support max_io_eqs for a function
Date: Mon, 8 Apr 2024 14:44:04 +0200	[thread overview]
Message-ID: <ZhPmlL_ptzw9PJ9z@nanopsycho> (raw)
In-Reply-To: <20240406010538.220167-3-parav@nvidia.com>

Sat, Apr 06, 2024 at 03:05:38AM CEST, parav@nvidia.com wrote:
>Implement get and set for the maximum IO event queues for SF and VF.
>This enables administrator on the hypervisor to control the maximum
>IO event queues which are typically used to derive the maximum and
>default number of net device channels or rdma device completion vectors.
>
>Reviewed-by: Shay Drory <shayd@nvidia.com>
>Signed-off-by: Parav Pandit <parav@nvidia.com>

Reviewed-by: Jiri Pirko <jiri@nvidia.com>

  parent reply	other threads:[~2024-04-08 12:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-06  1:05 [net-next v4 0/2] devlink: Add port function attribute for IO EQs Parav Pandit
2024-04-06  1:05 ` [net-next v4 1/2] devlink: Support setting max_io_eqs Parav Pandit
2024-04-06  1:05 ` [net-next v4 2/2] mlx5/core: Support max_io_eqs for a function Parav Pandit
2024-04-07 16:08   ` David Wei
2024-04-08 12:44   ` Jiri Pirko [this message]
2024-04-06  9:05 ` [net-next v4 0/2] devlink: Add port function attribute for IO EQs Zhu Yanjun
2024-04-08  3:20   ` Parav Pandit
2024-04-08 13:20 ` 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=ZhPmlL_ptzw9PJ9z@nanopsycho \
    --to=jiri@resnulli.us \
    --cc=corbet@lwn.net \
    --cc=danielj@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=dchumak@nvidia.com \
    --cc=dw@davidwei.uk \
    --cc=edumazet@google.com \
    --cc=kalesh-anakkur.purayil@broadcom.com \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=parav@nvidia.com \
    --cc=saeedm@nvidia.com \
    --cc=shayd@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