Netdev Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Parav Pandit <parav@nvidia.com>
To: Parav Pandit <parav@nvidia.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"kuba@kernel.org" <kuba@kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: RE: [PATCH net-next 00/10] devlink: Control auxiliary devices
Date: Tue, 10 Aug 2021 11:59:32 +0000	[thread overview]
Message-ID: <PH0PR12MB54819BFE1033C88504D5B256DCF79@PH0PR12MB5481.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20210810114620.8397-1-parav@nvidia.com>


> From: Parav Pandit <parav@nvidia.com>
> Sent: Tuesday, August 10, 2021 5:16 PM


> Hi Dave, Jakub,
> 
> Currently, for mlx5 multi-function device, a user is not able to control which
> functionality to enable/disable. For example, each PCI PF, VF, SF function by
> default has netdevice, RDMA and vdpa-net devices always enabled.
> 
> Hence, enable user to control which device functionality to enable/disable.
> 
> This is achieved by using existing devlink params [1] to enable/disable eth,
> rdma and vdpa net functionality control knob.
> 
> For example user interested in only vdpa device function: performs,
> 
> $ devlink dev param set pci/0000:06:00.0 name enable_rdma value false \
>                    cmode driverinit
> $ devlink dev param set pci/0000:06:00.0 name enable_eth value false \
>                    cmode driverinit
> $ devlink dev param set pci/0000:06:00.0 name enable_vnet value true \
>                    cmode driverinit

I missed to CC rdma and virt mailing list.
I am resending the series to CC them.

      parent reply	other threads:[~2021-08-10 11:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-10 11:46 Parav Pandit
2021-08-10 11:46 ` [PATCH net-next 01/10] devlink: Add new "enable_eth" generic device param Parav Pandit
2021-08-10 11:46 ` [PATCH net-next 02/10] devlink: Add new "enable_rdma" " Parav Pandit
2021-08-10 11:46 ` [PATCH net-next 03/10] devlink: Add new "enable_vnet" " Parav Pandit
2021-08-10 11:46 ` [PATCH net-next 04/10] devlink: Create a helper function for one parameter registration Parav Pandit
2021-08-10 11:46 ` [PATCH net-next 05/10] devlink: Add API to register and unregister single parameter Parav Pandit
2021-08-10 11:46 ` [PATCH net-next 06/10] devlink: Add APIs to publish, unpublish individual parameter Parav Pandit
2021-08-10 11:46 ` [PATCH net-next 07/10] net/mlx5: Fix unpublish devlink parameters Parav Pandit
2021-08-10 11:46 ` [PATCH net-next 08/10] net/mlx5: Support enable_eth devlink dev param Parav Pandit
2021-08-10 11:46 ` [PATCH net-next 09/10] net/mlx5: Support enable_rdma " Parav Pandit
2021-08-10 11:46 ` [PATCH net-next 10/10] net/mlx5: Support enable_vnet " Parav Pandit
2021-08-10 11:59 ` Parav Pandit [this message]

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=PH0PR12MB54819BFE1033C88504D5B256DCF79@PH0PR12MB5481.namprd12.prod.outlook.com \
    --to=parav@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --subject='RE: [PATCH net-next 00/10] devlink: Control auxiliary devices' \
    /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

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).