From: Gleb Natapov <gleb@cloudius-systems.com>
To: mst@redhat.com
Cc: kvm@vger.kernel.org
Subject: vhost + multiqueue + RSS question.
Date: Sun, 16 Nov 2014 18:18:18 +0200 [thread overview]
Message-ID: <20141116161818.GD7589@cloudius-systems.com> (raw)
Hi Michael,
I am playing with vhost multiqueue capability and have a question about
vhost multiqueue and RSS (receive side steering). My setup has Mellanox
ConnectX-3 NIC which supports multiqueue and RSS. Network related
parameters for qemu are:
-netdev tap,id=hn0,script=qemu-ifup.sh,vhost=on,queues=4
-device virtio-net-pci,netdev=hn0,id=nic1,mq=on,vectors=10
In a guest I ran "ethtool -L eth0 combined 4" to enable multiqueue.
I am running one tcp stream into the guest using iperf. Since there is
only one tcp stream I expect it to be handled by one queue only but
this seams to be not the case. ethtool -S on a host shows that the
stream is handled by one queue in the NIC, just like I would expect,
but in a guest all 4 virtio-input interrupt are incremented. Am I
missing any configuration?
--
Gleb.
next reply other threads:[~2014-11-16 16:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-16 16:18 Gleb Natapov [this message]
2014-11-16 18:56 ` vhost + multiqueue + RSS question Michael S. Tsirkin
2014-11-17 4:54 ` Venkateswara Rao Nandigam
2014-11-17 4:54 ` Venkateswara Rao Nandigam
2014-11-17 5:39 ` Jason Wang
2014-11-17 5:30 ` Jason Wang
2014-11-17 7:26 ` Gleb Natapov
2014-11-17 7:26 ` Gleb Natapov
2014-11-17 7:44 ` Gleb Natapov
2014-11-17 7:44 ` Gleb Natapov
2014-11-17 10:38 ` Michael S. Tsirkin
2014-11-17 11:22 ` Gleb Natapov
2014-11-17 11:58 ` Michael S. Tsirkin
2014-11-17 11:58 ` Michael S. Tsirkin
2014-11-17 12:22 ` Gleb Natapov
2014-11-18 1:37 ` Zhang Haoyu
2014-11-18 3:41 ` Jason Wang
2014-11-18 7:56 ` Gleb Natapov
2014-11-18 7:56 ` Gleb Natapov
2014-11-17 12:22 ` Gleb Natapov
2014-11-18 3:37 ` Jason Wang
2014-11-18 11:05 ` Michael S. Tsirkin
2014-11-19 3:01 ` Jason Wang
2014-11-17 11:22 ` Gleb Natapov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141116161818.GD7589@cloudius-systems.com \
--to=gleb@cloudius-systems.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.