From: Shirley Ma <mashirle@us.ibm.com>
To: "mst@redhat.com" <mst@redhat.com>, David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [RFC PATCH 0/1] vhost: Reduce TX used buffer signal for performance
Date: Wed, 27 Oct 2010 14:00:57 -0700 [thread overview]
Message-ID: <1288213257.17571.25.camel@localhost.localdomain> (raw)
This patch will change vhost TX used buffer guest signaling from one by
one to 3/4 ring size. I have tried different size, like 4, 16, 1/4 size,
1/2 size, and found that the large size is best for message size between
256 - 4K with netperf TCP_STREAM test, so 3/4 of the ring size is picked
up for signaling.
Tested both UDP and TCP performance with guest 2vcpu. The 60 secs
netperf run shows that guest to host performance for TCP.
TCP_STREAM
Message size Guest CPU(%) BW (Mb/s)
before:after before:after
256 57.84:58.42 1678.47:1908.75
512 68.68:60.21 1844.18:3387.33
1024 68.01:58.70 1945.14:3384.72
2048 65.36:54.25 2342.45:3799.31
4096 63.25:54.62 3307.11:4451.78
8192 59.57:57.89 6038.64:6694.04
UDP_STREAM
1024 49.64:26.69 1161.0:1687.6
2048 49.88:29.25 2326.8:2850.9
4096 49.59:29.15 3871.1:4880.3
8192 46.09:32.66 6822.9:7825.1
16K 42.90:34.96 11347.1:11767.4
For large message size, 60 secs run remains almost the same. I guess the
signal might not play a big role in large message transmission.
Shirley
next reply other threads:[~2010-10-27 21:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 21:00 Shirley Ma [this message]
2010-10-27 21:05 ` [RFC PATCH 0/1] vhost: Reduce TX used buffer signal for performance Shirley Ma
2010-10-28 8:57 ` Stefan Hajnoczi
2010-10-28 8:59 ` Stefan Hajnoczi
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=1288213257.17571.25.camel@localhost.localdomain \
--to=mashirle@us.ibm.com \
--cc=davem@davemloft.net \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).