Thread (46 messages) 46 messages, 10 authors, 2012-08-09

Re: [net-next RFC V5 4/5] virtio_net: multiqueue support

From: "Michael S. Tsirkin" <mst@redhat.com>
Date: 2012-07-29 09:44:30
Also in: kvm, lkml, netdev

On Sat, Jul 21, 2012 at 02:02:58PM +0200, Sasha Levin wrote:
On 07/20/2012 03:40 PM, Michael S. Tsirkin wrote:
quoted
quoted
-	err = init_vqs(vi);
quoted
+	if (virtio_has_feature(vdev, VIRTIO_NET_F_CTRL_VQ))
+		vi->has_cvq = true;
+
How about we disable multiqueue if there's no cvq?
Will make logic a bit simpler, won't it?
multiqueues don't really depend on cvq. Does this added complexity really justifies adding an artificial limit?
Well !cvq support is a legacy feature: the reason we support it
in driver is to avoid breaking on old hosts. Adding more code to that
path just doesn't make much sense since old hosts won't have mq.

-- 
MST
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help