From: "Michael S. Tsirkin" <mst@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: ERANRA@il.ibm.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, razya@il.ibm.com,
GLIKSON@il.ibm.com, YOSSIKU@il.ibm.com, abel.gordon@gmail.com,
JOELN@il.ibm.com, netdev@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] vhost: Add polling mode
Date: Tue, 12 Aug 2014 11:18:50 +0200 [thread overview]
Message-ID: <20140812091850.GD6440@redhat.com> (raw)
In-Reply-To: <20140811.124621.576073630604147753.davem@davemloft.net>
On Mon, Aug 11, 2014 at 12:46:21PM -0700, David Miller wrote:
> From: "Michael S. Tsirkin" <mst@redhat.com>
> Date: Sun, 10 Aug 2014 21:45:59 +0200
>
> > On Sun, Aug 10, 2014 at 11:30:35AM +0300, Razya Ladelsky wrote:
> ...
> > And, did your tests actually produce 100% load on both host CPUs?
> ...
>
> Michael, please do not quote an entire patch just to ask a one line
> question.
>
> I truly, truly, wish it was simpler in modern email clients to delete
> the unrelated quoted material because I bet when people do this they
> are simply being lazy.
>
> Thank you.
Lazy - mea culpa, though I'm using mutt so it isn't even hard.
The question still stands: the test results are only valid
if CPU was at 100% in all configurations.
This is the reason I generally prefer it when people report
throughput divided by CPU (power would be good too but it still
isn't easy for people to get that number).
--
MST
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: razya@il.ibm.com, kvm@vger.kernel.org, GLIKSON@il.ibm.com,
ERANRA@il.ibm.com, YOSSIKU@il.ibm.com, JOELN@il.ibm.com,
abel.gordon@gmail.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] vhost: Add polling mode
Date: Tue, 12 Aug 2014 11:18:50 +0200 [thread overview]
Message-ID: <20140812091850.GD6440@redhat.com> (raw)
In-Reply-To: <20140811.124621.576073630604147753.davem@davemloft.net>
On Mon, Aug 11, 2014 at 12:46:21PM -0700, David Miller wrote:
> From: "Michael S. Tsirkin" <mst@redhat.com>
> Date: Sun, 10 Aug 2014 21:45:59 +0200
>
> > On Sun, Aug 10, 2014 at 11:30:35AM +0300, Razya Ladelsky wrote:
> ...
> > And, did your tests actually produce 100% load on both host CPUs?
> ...
>
> Michael, please do not quote an entire patch just to ask a one line
> question.
>
> I truly, truly, wish it was simpler in modern email clients to delete
> the unrelated quoted material because I bet when people do this they
> are simply being lazy.
>
> Thank you.
Lazy - mea culpa, though I'm using mutt so it isn't even hard.
The question still stands: the test results are only valid
if CPU was at 100% in all configurations.
This is the reason I generally prefer it when people report
throughput divided by CPU (power would be good too but it still
isn't easy for people to get that number).
--
MST
next prev parent reply other threads:[~2014-08-12 9:18 UTC|newest]
Thread overview: 55+ 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 19:45 ` Michael S. Tsirkin
2014-08-10 19:45 ` Michael S. Tsirkin
2014-08-11 19:46 ` David Miller
2014-08-11 19:46 ` David Miller
2014-08-12 9:18 ` Michael S. Tsirkin [this message]
2014-08-12 9:18 ` Michael S. Tsirkin
2014-08-12 10:57 ` Razya Ladelsky
2014-08-12 10:57 ` Razya Ladelsky
2014-08-13 12:15 ` Michael S. Tsirkin
2014-08-13 12:15 ` Michael S. Tsirkin
2014-08-17 12:35 ` Razya Ladelsky
2014-08-17 12:35 ` Razya Ladelsky
2014-08-17 12:58 ` Michael S. Tsirkin
2014-08-17 12:58 ` Michael S. Tsirkin
2014-08-19 8:36 ` Razya Ladelsky
2014-08-19 8:36 ` Razya Ladelsky
2014-08-20 11:05 ` Michael S. Tsirkin
2014-08-20 11:05 ` Michael S. Tsirkin
2016-09-04 8:45 ` Razya Ladelsky
2016-09-04 8:45 ` Razya Ladelsky
2014-08-20 8:41 ` Christian Borntraeger
2014-08-20 8:41 ` Christian Borntraeger
2014-08-20 10:32 ` Michael S. Tsirkin
2014-08-20 10:32 ` Michael S. Tsirkin
2014-08-21 13:53 ` Razya Ladelsky
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-20 10:57 ` Michael S. Tsirkin
2014-08-21 14:23 ` Razya Ladelsky
2014-08-21 14:23 ` Razya Ladelsky
2014-08-21 14:29 ` David Laight
2014-08-21 14:29 ` David Laight
2014-08-24 12:26 ` Razya Ladelsky
2014-08-24 12:26 ` Razya Ladelsky
2014-08-10 8:30 ` Razya Ladelsky
2014-08-10 8:30 ` Razya Ladelsky
2014-08-10 8:30 ` Razya Ladelsky
2014-07-21 13:23 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
2014-07-29 12:23 ` Razya Ladelsky
2014-07-29 12:40 ` Michael S. Tsirkin
2014-07-30 6:32 ` 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=20140812091850.GD6440@redhat.com \
--to=mst@redhat.com \
--cc=ERANRA@il.ibm.com \
--cc=GLIKSON@il.ibm.com \
--cc=JOELN@il.ibm.com \
--cc=YOSSIKU@il.ibm.com \
--cc=abel.gordon@gmail.com \
--cc=davem@davemloft.net \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=razya@il.ibm.com \
--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 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.