[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AM0PR0502MB36837D5478983730B6ADEFEBBF440@AM0PR0502MB3683.eurprd05.prod.outlook.com>
Date: Wed, 25 Oct 2017 05:41:07 +0000
From: Yuval Mintz <yuvalm@...lanox.com>
To: Steve Lin <steven.lin1@...adcom.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
CC: Jiri Pirko <jiri@...lanox.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"michael.chan@...adcom.com" <michael.chan@...adcom.com>,
"linville@...driver.com" <linville@...driver.com>,
"gospo@...adcom.com" <gospo@...adcom.com>
Subject: RE: [PATCH net-next v3 03/10] devlink: Adding num VFs per PF
permanent config param
> Adding DEVLINK_PERM_CONFIG_NUM_VF_PER_PF permanent config
> parameter. Value is permanent, so becomes the new default
> value for this device.
>
> The value sets the number of VFs per PF in SR-IOV mode.
Assuming it's meant to directly control the PCIe capability value
I think you should mention it explicitly in the commit message.
Powered by blists - more mailing lists