summaryrefslogtreecommitdiffstats
path: root/arch/mn10300
diff options
context:
space:
mode:
authorKY Srinivasan <kys@microsoft.com>2015-05-27 13:16:57 -0700
committerDavid S. Miller <davem@davemloft.net>2015-05-30 17:38:44 -0700
commite01ec2199ef22e2cabd7d6e68a192f3eb728029f (patch)
tree8b85d6e5667092dd5f9cb083685c6d6e61f1b560 /arch/mn10300
parent8133534c760d4083f79d2cde42c636ccc0b2792e (diff)
downloadop-kernel-dev-e01ec2199ef22e2cabd7d6e68a192f3eb728029f.zip
op-kernel-dev-e01ec2199ef22e2cabd7d6e68a192f3eb728029f.tar.gz
hv_netvsc: Properly size the vrss queues
The current algorithm for deciding on the number of VRSS channels is not optimal since we open up the min of number of CPUs online and the number of VRSS channels the host is offering. So on a 32 VCPU guest we could potentially open 32 VRSS subchannels. Experimentation has shown that it is best to limit the number of VRSS channels to the number of CPUs within a NUMA node. Here is the new algorithm for deciding on the number of sub-channels we would open up: 1) Pick the minimum of what the host is offering and what the driver in the guest is specifying as the default value. 2) Pick the minimum of (1) and the numbers of CPUs in the NUMA node the primary channel is bound to. Signed-off-by: K. Y. Srinivasan <kys@microsoft.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'arch/mn10300')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud