netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Samudrala, Sridhar" <sridhar.samudrala@intel.com>
To: Parav Pandit <parav@nvidia.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"dsahern@kernel.org" <dsahern@kernel.org>,
	"stephen@networkplumber.org" <stephen@networkplumber.org>
Cc: Jiri Pirko <jiri@nvidia.com>, Shay Drori <shayd@nvidia.com>
Subject: Re: [PATCH v2 0/2] devlink: Support setting max_io_eqs
Date: Thu, 11 Apr 2024 18:03:56 -0500	[thread overview]
Message-ID: <dc7eb252-5223-4475-9607-9cf1fc81b486@intel.com> (raw)
In-Reply-To: <PH0PR12MB5481898C4B58CF660B1603DDDC052@PH0PR12MB5481.namprd12.prod.outlook.com>



On 4/10/2024 9:32 PM, Parav Pandit wrote:
> Hi Sridhar,
> 
>> From: Samudrala, Sridhar <sridhar.samudrala@intel.com>
>> Sent: Thursday, April 11, 2024 4:53 AM
>>
>>
>> On 4/10/2024 6:58 AM, Parav Pandit wrote:
>>> Devices send event notifications for the IO queues, such as tx and rx
>>> queues, through event queues.
>>>
>>> Enable a privileged owner, such as a hypervisor PF, to set the number
>>> of IO event queues for the VF and SF during the provisioning stage.
>>
>> How do you provision tx/rx queues for VFs & SFs?
>> Don't you need similar mechanism to setup max tx/rx queues too?
> 
> Currently we don’t. They are derived from the IO event queues.
> As you know, sometimes more txqs than IO event queues needed for XDP, timestamp, multiple TCs.
> If needed, probably additional knob for txq, rxq can be added to restrict device resources.

Rather than deriving tx and rx queues from IO event queues, isn't it 
more user friendly to do the other way. Let the host admin set the max 
number of tx and rx queues allowed and the driver derive the number of 
ioevent queues based on those values. This will be consistent with what 
ethtool reports as pre-set maximum values for the corresponding VF/SF.


> 
>>
>>
>>>
>>> example:
>>> Get maximum IO event queues of the VF device::
>>>
>>>     $ devlink port show pci/0000:06:00.0/2
>>>     pci/0000:06:00.0/2: type eth netdev enp6s0pf0vf1 flavour pcivf pfnum 0
>> vfnum 1
>>>         function:
>>>             hw_addr 00:00:00:00:00:00 ipsec_packet disabled max_io_eqs
>>> 10
>>>
>>> Set maximum IO event queues of the VF device::
>>>
>>>     $ devlink port function set pci/0000:06:00.0/2 max_io_eqs 32
>>>
>>>     $ devlink port show pci/0000:06:00.0/2
>>>     pci/0000:06:00.0/2: type eth netdev enp6s0pf0vf1 flavour pcivf pfnum 0
>> vfnum 1
>>>         function:
>>>             hw_addr 00:00:00:00:00:00 ipsec_packet disabled max_io_eqs
>>> 32
>>>
>>> patch summary:
>>> patch-1 updates devlink uapi
>>> patch-2 adds print, get and set routines for max_io_eqs field
>>>
>>> changelog:
>>> v1->v2:
>>> - addressed comments from Jiri
>>> - updated man page for the new parameter
>>> - corrected print to not have EQs value as optional
>>> - replaced 'value' with 'EQs'
>>>
>>> Parav Pandit (2):
>>>     uapi: Update devlink kernel headers
>>>     devlink: Support setting max_io_eqs
>>>
>>>    devlink/devlink.c            | 29 ++++++++++++++++++++++++++++-
>>>    include/uapi/linux/devlink.h |  1 +
>>>    man/man8/devlink-port.8      | 12 ++++++++++++
>>>    3 files changed, 41 insertions(+), 1 deletion(-)
>>>

  reply	other threads:[~2024-04-11 23:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-10 11:58 [PATCH v2 0/2] devlink: Support setting max_io_eqs Parav Pandit
2024-04-10 11:58 ` [PATCH v2 1/2] uapi: Update devlink kernel headers Parav Pandit
2024-04-10 11:58 ` [PATCH v2 2/2] devlink: Support setting max_io_eqs Parav Pandit
2024-04-10 23:22 ` [PATCH v2 0/2] " Samudrala, Sridhar
2024-04-11  2:32   ` Parav Pandit
2024-04-11 23:03     ` Samudrala, Sridhar [this message]
2024-04-12  2:06       ` David Ahern
2024-04-12  3:31         ` Parav Pandit
2024-04-12  5:22           ` Parav Pandit
2024-04-12 22:03             ` Samudrala, Sridhar
2024-04-13  2:01               ` Parav Pandit
2024-04-13 16:40 ` 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=dc7eb252-5223-4475-9607-9cf1fc81b486@intel.com \
    --to=sridhar.samudrala@intel.com \
    --cc=dsahern@kernel.org \
    --cc=jiri@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=parav@nvidia.com \
    --cc=shayd@nvidia.com \
    --cc=stephen@networkplumber.org \
    /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).