mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Ding Xiao <ssdxiaoding@gmail.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: how to optimize virtio-vhost in 10G net
Date: Sun, 15 Feb 2015 07:48:32 +0008	[thread overview]
Message-ID: <1423986032.21931.0@smtp.corp.redhat.com> (raw)
In-Reply-To: <CALmf_FLOFieevBqE4KbSPa3hB1iOU3ioD6SmDPU60aYmj8oHCQ@mail.gmail.com>



On Sun, Feb 15, 2015 at 3:30 PM, Ding Xiao <ssdxiaoding@gmail.com> 
wrote:
> I am test virtio-vhost in 10G environment
> 
> host info
> cpu E2680@2.7GHz
> memory 16G
> network intel 82599BE
> os centos 7
> 
> VM info
> cpu 4
> memory 4G
> network using virtio vhost
> os centos 7
> 
> I using pktgen to send udp package, the result like follow
> 64b 230Mb/s
> 1400b 5.9Gb/s
> 
> I test the speed in VMware too, the result like follow
> 64b 700Mb/s
> 1400 9.3Gb/s
> 
> I am very surprised why the speed with virtio-vhost is slow
> so I test to analysis this by using perf tool
> I found the tun_sendmsg occupancy rate of 35%

It looks like you're using pktgen in guest. Pktgen has known issue with 
driver that does not have tx completion. See discussion here: 
https://patchwork.kernel.org/patch/1800711/

So you can't trust pktgen result in this case.
> 
> tun_sendmsg using copy_from_user to get the data from VM
> Perhaps mapping could improve the performance ?

If you enable vhost_net zerocopy, you will see obvious improvements.
> 
> or other Another improvement method ?

I suggest that you can use other benchmark tools (or apply the patch in 
the above link with pktgen).
> 
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


      reply	other threads:[~2015-02-15  7:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-15  7:30 Ding Xiao
2015-02-15  7:40 ` Jason Wang [this message]

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=1423986032.21931.0@smtp.corp.redhat.com \
    --to=jasowang@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ssdxiaoding@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

all inboxes | Powered by JetHome®