[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AM0PR0502MB3683B79EBF09CB3837098581BF420@AM0PR0502MB3683.eurprd05.prod.outlook.com>
Date: Thu, 19 Oct 2017 10:36:52 +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 3/7] devlink: Adding high level dev perm config params
> DEVLINK_ATTR_PERM_CFG_MULTIFUNC_MODE: Configure multi-function
> mode; use devlink_multifunc_mode.
...
> +enum devlink_multifunc_mode {
> + DEVLINK_MULTIFUNC_MODE_ALLOWED, /* Ext switch
> activates MF */
> + DEVLINK_MULTIFUNC_MODE_FORCE_SINGFUNC,
> + DEVLINK_MULTIFUNC_MODE_NPAR10, /* NPAR 1.0
> */
> + DEVLINK_MULTIFUNC_MODE_NPAR15, /* NPAR 1.5
> */
> + DEVLINK_MULTIFUNC_MODE_NPAR20, /* NPAR 2.0
> */
> +};
... And when someone would invent a new partitioning scheme, what then?
You'd extend the 'generic' modes?
It's not very generic.
> DEVLINK_ATTR_PERM_CFG_SECURE_NIC_ENABLED: 1 to enable Secure NIC
> functionality, 0 to disable.
What does it mean? Is there some spec explaining it?
Powered by blists - more mailing lists