From: Asias He <asias.hejun@gmail.com>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: penberg@kernel.org, john@jfloren.net, kvm@vger.kernel.org,
mingo@elte.hu, gorcunov@gmail.com, prasadjoshi124@gmail.com
Subject: Re: [PATCH v2 3/4] kvm tools: Use ioeventfd in virtio-net
Date: Tue, 31 May 2011 07:53:18 +0800 [thread overview]
Message-ID: <4DE42DEE.8070906@gmail.com> (raw)
In-Reply-To: <1306513120-28794-3-git-send-email-levinsasha928@gmail.com>
On 05/28/2011 12:18 AM, Sasha Levin wrote:
> Use ioeventfds to receive notifications of IO events in virtio-net.
> Doing so prevents an exit every time we receive/send a packet.
>
> Signed-off-by: Sasha Levin <levinsasha928@gmail.com>
Hi, Sasha
Here below are the test results you asked yesterday with your ioeventfd
changes.
----------------------------------
TAP based network performance with ioeventfd
(host -> guest)
hj:~# netperf -c -t TCP_STREAM -H guest
TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to guest
(192.168.33.15) port 0 AF_INET : demo
Recv Send Send Utilization Service
Demand
Socket Socket Message Elapsed Send Recv Send Recv
Size Size Size Time Throughput local remote local
remote
bytes bytes bytes secs. 10^6bits/s % S % U us/KB us/KB
87380 16384 16384 10.00 5477.07 60.01 -1.00 3.590
-1.000
hj:~# netperf -c -t UDP_STREAM -H guest
UDP UNIDIRECTIONAL SEND TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to
guest (192.168.33.15) port 0 AF_INET : demo
Socket Message Elapsed Messages CPU Service
Size Size Time Okay Errors Throughput Util Demand
bytes bytes secs # # 10^6bits/sec % SU us/KB
114688 65507 10.00 221207 0 11592.2 73.33 8.368
110592 10.00 54793 2871.4 -1.00 -1.000
(guest-> host)
root@sid2:~# netperf -c -t TCP_STREAM -H host
TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to host
(192.168.33.2) port 0 AF_INET : demo
Recv Send Send Utilization Service
Demand
Socket Socket Message Elapsed Send Recv Send Recv
Size Size Size Time Throughput local remote local
remote
bytes bytes bytes secs. 10^6bits/s % S % U us/KB us/KB
87380 16384 16384 10.00 1724.30 98.70 -1.00 4.689
-1.000
root@sid2:~# netperf -c -t UDP_STREAM -H host
UDP UNIDIRECTIONAL SEND TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to
host (192.168.33.2) port 0 AF_INET : demo
Socket Message Elapsed Messages CPU Service
Size Size Time Okay Errors Throughput Util Demand
bytes bytes secs # # 10^6bits/sec % SU us/KB
110592 65507 10.00 117986 0 6182.8 99.90 1.364
114688 10.00 114480 5999.1 -1.00 -1.000
--
Best Regards,
Asias He
next prev parent reply other threads:[~2011-05-30 23:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-27 16:18 [PATCH v2 1/4] kvm tools: Add ioeventfd support Sasha Levin
2011-05-27 16:18 ` [PATCH v2 2/4] kvm tools: Use ioeventfd in virtio-blk Sasha Levin
2011-05-27 16:18 ` [PATCH v2 3/4] kvm tools: Use ioeventfd in virtio-net Sasha Levin
2011-05-29 12:51 ` Ingo Molnar
2011-05-30 23:53 ` Asias He [this message]
2011-05-31 7:18 ` Pekka Enberg
2011-05-31 16:32 ` Sasha Levin
2011-06-01 1:41 ` Asias He
2011-06-01 6:35 ` Sasha Levin
2011-06-01 11:11 ` Asias He
2011-05-27 16:18 ` [PATCH v2 4/4] kvm tools: Use ioeventfd in virtio-rng Sasha Levin
2011-05-27 16:52 ` [PATCH v2 1/4] kvm tools: Add ioeventfd support Ingo Molnar
2011-05-29 11:55 ` Pekka Enberg
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=4DE42DEE.8070906@gmail.com \
--to=asias.hejun@gmail.com \
--cc=gorcunov@gmail.com \
--cc=john@jfloren.net \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=mingo@elte.hu \
--cc=penberg@kernel.org \
--cc=prasadjoshi124@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox