From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gleb Natapov <gleb@cloudius-systems.com>
Cc: kvm@vger.kernel.org, virtualization@lists.linux-foundation.org
Subject: Re: vhost + multiqueue + RSS question.
Date: Mon, 17 Nov 2014 12:38:16 +0200 [thread overview]
Message-ID: <20141117103816.GA20638@redhat.com> (raw)
In-Reply-To: <20141117074423.GG7589@cloudius-systems.com>
On Mon, Nov 17, 2014 at 09:44:23AM +0200, Gleb Natapov wrote:
> On Sun, Nov 16, 2014 at 08:56:04PM +0200, Michael S. Tsirkin wrote:
> > On Sun, Nov 16, 2014 at 06:18:18PM +0200, Gleb Natapov wrote:
> > > 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?
> >
> > I don't see anything obviously wrong with what you describe.
> > Maybe, somehow, same irqfd got bound to multiple MSI vectors?
> It does not look like this is what is happening judging by the way
> interrupts are distributed between queues. They are not distributed
> uniformly and often I see one queue gets most interrupt and others get
> much less and then it changes.
Weird. It would happen if you transmitted from multiple CPUs.
You did pin iperf to a single CPU within guest, did you not?
> --
> Gleb.
next prev parent reply other threads:[~2014-11-17 10:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20141116161818.GD7589@cloudius-systems.com>
2014-11-16 18:56 ` vhost + multiqueue + RSS question Michael S. Tsirkin
2014-11-17 4:54 ` Venkateswara Rao Nandigam
2014-11-17 5:30 ` Jason Wang
2014-11-17 7:26 ` Gleb Natapov
[not found] ` <5CC583AB71FC0C44A5CAB54823E83A8422B8ABD4@SINPEX01CL01.citrite.net>
2014-11-17 5:39 ` Jason Wang
2014-11-17 7:44 ` Gleb Natapov
[not found] ` <20141117074423.GG7589@cloudius-systems.com>
2014-11-17 10:38 ` Michael S. Tsirkin [this message]
2014-11-17 11:22 ` Gleb Natapov
[not found] ` <20141117112207.GJ7589@cloudius-systems.com>
2014-11-17 11:58 ` Michael S. Tsirkin
[not found] ` <20141117115820.GA10709@redhat.com>
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
[not found] ` <20141117122214.GK7589@cloudius-systems.com>
[not found] ` <201411180937499909334@sangfor.com>
2014-11-18 3:41 ` Jason Wang
2014-11-18 7:56 ` 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=20141117103816.GA20638@redhat.com \
--to=mst@redhat.com \
--cc=gleb@cloudius-systems.com \
--cc=kvm@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).