From: "Michael S. Tsirkin" <mst@redhat.com>
To: Razya Ladelsky <RAZYA@il.ibm.com>
Cc: Eran Raichstein <ERANRA@il.ibm.com>,
kvm-owner@vger.kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, abel.gordon@gmail.com,
Alex Glikson <GLIKSON@il.ibm.com>,
Yossi Kuperman1 <YOSSIKU@il.ibm.com>,
Joel Nider <JOELN@il.ibm.com>,
netdev@vger.kernel.org,
virtualization@lists.linux-foundation.org,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH] vhost: Add polling mode
Date: Wed, 20 Aug 2014 13:05:15 +0200 [thread overview]
Message-ID: <20140820110515.GD17371@redhat.com> (raw)
In-Reply-To: <OFB79DEF3C.1ADC0F14-ONC2257D39.002F0F0A-C2257D39.002F3CBC@il.ibm.com>
On Tue, Aug 19, 2014 at 11:36:31AM +0300, Razya Ladelsky wrote:
> > That was just one example. There many other possibilities. Either
> > actually make the systems load all host CPUs equally, or divide
> > throughput by host CPU.
> >
>
> The polling patch adds this capability to vhost, reducing costly exit
> overhead when the vm is loaded.
>
> In order to load the vm I ran netperf with msg size of 256:
>
> Without polling: 2480 Mbits/sec, utilization: vm - 100% vhost - 64%
> With Polling: 4160 Mbits/sec, utilization: vm - 100% vhost - 100%
>
> Therefore, throughput/cpu without polling is 15.1, and 20.8 with polling.
>
Can you please present results in a form that makes
it possible to see the effect on various configurations
and workloads?
Here's one example where this was done:
https://lkml.org/lkml/2014/8/14/495
You really should also provide data about your host
configuration (missing in the above link).
> My intention was to load vhost as close as possible to 100% utilization
> without polling, in order to compare it to the polling utilization case
> (where vhost is always 100%).
> The best use case, of course, would be when the shared vhost thread work
> (TBD) is integrated and then vhost will actually be using its polling
> cycles to handle requests of multiple devices (even from multiple vms).
>
> Thanks,
> Razya
--
MST
next prev parent reply other threads:[~2014-08-20 11:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1407659404-razya@il.ibm.com>
2014-08-10 8:30 ` [PATCH] vhost: Add polling mode Razya Ladelsky
2014-08-10 8:30 ` Razya Ladelsky
2014-08-10 8:30 ` Razya Ladelsky
2014-08-10 19:45 ` Michael S. Tsirkin
2014-08-11 19:46 ` David Miller
2014-08-12 9:18 ` Michael S. Tsirkin
2014-08-12 10:57 ` Razya Ladelsky
2014-08-13 12:15 ` Michael S. Tsirkin
2014-08-17 12:35 ` Razya Ladelsky
2014-08-17 12:58 ` Michael S. Tsirkin
2014-08-19 8:36 ` Razya Ladelsky
2014-08-20 11:05 ` Michael S. Tsirkin [this message]
2016-09-04 8:45 ` Razya Ladelsky
2014-08-20 8:41 ` Christian Borntraeger
2014-08-20 10:32 ` Michael S. Tsirkin
2014-08-21 13:53 ` Razya Ladelsky
2014-08-22 9:30 ` Zhang Haoyu
2014-08-22 10:01 ` Zhang Haoyu
2014-08-20 10:57 ` Michael S. Tsirkin
2014-08-21 14:23 ` Razya Ladelsky
2014-08-21 14:29 ` David Laight
2014-08-24 12:26 ` Razya Ladelsky
2014-08-10 8:30 ` Razya Ladelsky
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=20140820110515.GD17371@redhat.com \
--to=mst@redhat.com \
--cc=ERANRA@il.ibm.com \
--cc=GLIKSON@il.ibm.com \
--cc=JOELN@il.ibm.com \
--cc=RAZYA@il.ibm.com \
--cc=YOSSIKU@il.ibm.com \
--cc=abel.gordon@gmail.com \
--cc=davem@davemloft.net \
--cc=kvm-owner@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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).