public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Razya Ladelsky <RAZYA@il.ibm.com>
Cc: abel.gordon@gmail.com, Alex Glikson <GLIKSON@il.ibm.com>,
	Eran Raichstein <ERANRA@il.ibm.com>,
	Joel Nider <JOELN@il.ibm.com>,
	kvm@vger.kernel.org, Yossi Kuperman1 <YOSSIKU@il.ibm.com>
Subject: Re: [PATCH] vhost: Add polling mode
Date: Tue, 29 Jul 2014 12:44:36 +0200	[thread overview]
Message-ID: <20140729104436.GB13388@redhat.com> (raw)
In-Reply-To: <OF2B469B7C.BD190841-ONC2257D24.0038AEE5-C2257D24.0039AB18@il.ibm.com>

On Tue, Jul 29, 2014 at 01:30:03PM +0300, Razya Ladelsky wrote:

[..] had to snip off the quoted text, it's mangled up to
     unreadability.
Please take a look at Documentation/email-clients.txt
to fix this.

> > This is an optimization patch, isn't it?
> > Could you please include some numbers showing its
> > effect?
> > 
> > 
> 
> Hi Michael,
> Sure. I included them in a reply to Jason Wang in this thread,
> Here it is:
> http://www.spinics.net/linux/lists/kvm/msg106049.html
> 

Hmm there aren't a lot of numbers there :(. Speed increased by 33% but
by how much?  E.g. maybe you are getting from 1Mbyte/sec to 1.3,
if so it's hard to get excited about it. Some questions that come to
mind: what was the message size? I would expect several measurements
with different values.  How did host CPU utilization change?

What about latency? As we are competing with guest for host CPU,
would worst-case or average latency suffer?

Thanks,

-- 
MST

  reply	other threads:[~2014-07-29 10:44 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-21 13:23 [PATCH] vhost: Add polling mode Razya Ladelsky
2014-07-23  5:26 ` Jason Wang
2014-07-23  8:12   ` Razya Ladelsky
2014-07-23  8:42     ` Jason Wang
2014-07-23  8:48       ` Abel Gordon
2014-07-24  5:57         ` Jason Wang
2014-07-29  1:30         ` Zhang Haoyu
2014-07-29  7:15           ` Razya Ladelsky
2014-07-29  8:06 ` Michael S. Tsirkin
2014-07-29 10:30   ` Razya Ladelsky
2014-07-29 10:44     ` Michael S. Tsirkin [this message]
2014-07-29 12:23       ` Razya Ladelsky
2014-07-29 12:40         ` Michael S. Tsirkin
2014-07-30  6:32           ` Razya Ladelsky
     [not found] <1407659404-razya@il.ibm.com>
2014-08-10  8:30 ` 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
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=20140729104436.GB13388@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=kvm@vger.kernel.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