xen-netback: respect user provided max_queues
Originally that parameter was always reset to num_online_cpus during module initialisation, which renders it useless. The fix is to only set max_queues to num_online_cpus when user has not provided a value. Reported-by: Johnny Strom <johnny.strom@linuxsolutions.fi> Signed-off-by: Wei Liu <wei.liu2@citrix.com> Reviewed-by: David Vrabel <david.vrabel@citrix.com> Acked-by: Ian Campbell <ian.campbell@citrix.com> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
parent
420203204e
commit
4c82ac3c37
1 changed files with 5 additions and 2 deletions
|
@ -2114,8 +2114,11 @@ static int __init netback_init(void)
|
|||
if (!xen_domain())
|
||||
return -ENODEV;
|
||||
|
||||
/* Allow as many queues as there are CPUs, by default */
|
||||
xenvif_max_queues = num_online_cpus();
|
||||
/* Allow as many queues as there are CPUs if user has not
|
||||
* specified a value.
|
||||
*/
|
||||
if (xenvif_max_queues == 0)
|
||||
xenvif_max_queues = num_online_cpus();
|
||||
|
||||
if (fatal_skb_slots < XEN_NETBK_LEGACY_SLOTS_MAX) {
|
||||
pr_info("fatal_skb_slots too small (%d), bump it to XEN_NETBK_LEGACY_SLOTS_MAX (%d)\n",
|
||||
|
|
Loading…
Reference in a new issue