Bug 1309274 - [RFE] set vnic queue# intelligently
Summary: [RFE] set vnic queue# intelligently
Keywords:
Status: CLOSED DUPLICATE of bug 1574771
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RFEs
Version: 3.6.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Yaniv Lavi
QA Contact: Meni Yakove
URL:
Whiteboard:
Depends On: 1258206 1293233
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-17 11:07 UTC by Dan Kenigsberg
Modified: 2019-04-28 09:41 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of: 1258206
Environment:
Last Closed: 2018-06-06 07:47:56 UTC
oVirt Team: Network
Embargoed:
ylavi: ovirt-future?
danken: planning_ack?
danken: devel_ack?
danken: testing_ack?


Attachments (Terms of Use)

Description Dan Kenigsberg 2016-02-17 11:07:22 UTC
There are use cases where setting multiple queues per vnic makes sense (e.g running two multi-vcpu heavily-intercommunicating VMs on the same host).

Setting multiple queues has a (minor) side effect of wasting host memory.

This RFE tracks a request to have a smarter policy of setting the number of queues: we'd like to make it equal to the number of vcpu, unless another number is requested by the VM admin.

Queues should be set only on virtio vnics; in particular, they should not set on passed-through vnics.


http://libvirt.org/formatdomain.html#elementsDriverBackendOptions

queues
    The optional queues attribute controls the number of queues to be used for either Multiqueue virtio-net or vhost-user network interfaces. Use of multiple packet processing queues requires the interface having the <model type='virtio'/> element. Each queue will potentially be handled by a different processor, resulting in much higher throughput. virtio-net since 1.0.6 (QEMU and KVM only) vhost-user since 1.2.17 (QEMU and KVM only)

Comment 6 Yaniv Lavi 2018-06-06 07:47:56 UTC

*** This bug has been marked as a duplicate of bug 1574771 ***


Note You need to log in before you can comment on or make changes to this bug.