From: Raghu Vatsavayi <rvatsav...@caviumnetworks.com>
Date: Wed, 19 Oct 2016 22:40:38 -0700
> +/* Default behaviour of Liquidio is to provide one queue per VF. But Liquidio
> + * can also provide multiple queues to each VF. If user wants to change the
> + * default behaviour HW should be provided configuration info at init time,
> + * based on which it will create control queues for communicating with FW.
> + */
> +static u32 max_vfs[2] = { 0, 0 };
> +module_param_array(max_vfs, int, NULL, 0444);
> +MODULE_PARM_DESC(max_vfs, "Assign two comma-separated unsigned integers that
> specify max number of VFs for PF0 (left of the comma) and PF1 (right of the
> comma); for 23xx only. By default HW will configure as many VFs as queues
> after allocating PF queues.To increase queues for VF use this parameter. Use
> sysfs to create these VFs.");
> +
> +static unsigned int num_queues_per_pf[2] = { 0, 0 };
> +module_param_array(num_queues_per_pf, uint, NULL, 0444);
> +MODULE_PARM_DESC(num_queues_per_pf, "two comma-separated unsigned integers
> that specify number of queues per PF0 (left of the comma) and PF1 (right of
> the comma); for 23xx only");
> +
> static int ptp_enable = 1;
We cannot continue to allow drivers to add custom module parameters to
control this. It is the worst user experience possible.
We need a tree-wide generic, consistent, manner in which to configure
and control this kind of thing.
