All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesper Dangaard Brouer <brouer@redhat.com>
To: xiangxia.m.yue@gmail.com
Cc: mst@redhat.com, netdev@vger.kernel.org, brouer@redhat.com,
	virtualization@lists.linux-foundation.org,
	Tonghao Zhang <zhangtonghao@didichuxing.com>
Subject: Re: [PATCH net-next v3 4/4] net: vhost: add rx busy polling in tx path
Date: Sat, 30 Jun 2018 09:03:03 +0200	[thread overview]
Message-ID: <20180630090303.043a06c7@redhat.com> (raw)
In-Reply-To: <1530340438-3039-5-git-send-email-xiangxia.m.yue@gmail.com>

On Fri, 29 Jun 2018 23:33:58 -0700
xiangxia.m.yue@gmail.com wrote:

> From: Tonghao Zhang <xiangxia.m.yue@gmail.com>
> 
> This patch improves the guest receive and transmit performance.
> On the handle_tx side, we poll the sock receive queue at the
> same time. handle_rx do that in the same way.
> 
> We set the poll-us=100us and use the iperf3 to test

Where/how do you configure poll-us=100us ?

Are you talking about /proc/sys/net/core/busy_poll ?


p.s. Nice performance boost! :-)

> its bandwidth, use the netperf to test throughput and mean
> latency. When running the tests, the vhost-net kthread of
> that VM, is alway 100% CPU. The commands are shown as below.
> 
> iperf3  -s -D
> iperf3  -c IP -i 1 -P 1 -t 20 -M 1400
> 
> or
> netserver
> netperf -H IP -t TCP_RR -l 20 -- -O "THROUGHPUT,MEAN_LATENCY"
> 
> host -> guest:
> iperf3:
> * With the patch:     27.0 Gbits/sec
> * Without the patch:  14.4 Gbits/sec
> 
> netperf (TCP_RR):
> * With the patch:     48039.56 trans/s, 20.64us mean latency
> * Without the patch:  46027.07 trans/s, 21.58us mean latency
> 
> This patch also improves the guest transmit performance.
> 
> guest -> host:
> iperf3:
> * With the patch:     27.2 Gbits/sec
> * Without the patch:  24.4 Gbits/sec
> 
> netperf (TCP_RR):
> * With the patch:     47963.25 trans/s, 20.71us mean latency
> * Without the patch:  45796.70 trans/s, 21.68us mean latency
> 
> Signed-off-by: Tonghao Zhang <zhangtonghao@didichuxing.com>

-- 
Best regards,
  Jesper Dangaard Brouer
  MSc.CS, Principal Kernel Engineer at Red Hat
  LinkedIn: http://www.linkedin.com/in/brouer

  reply	other threads:[~2018-06-30  7:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-30  6:33 [PATCH net-next v3 0/4] net: vhost: improve performance when enable busyloop xiangxia.m.yue
2018-06-30  6:33 ` [PATCH net-next v3 1/4] net: vhost: lock the vqs one by one xiangxia.m.yue
2018-07-02  2:21   ` Jason Wang
2018-07-02  2:21   ` Jason Wang
2018-06-30  6:33 ` xiangxia.m.yue
2018-06-30  6:33 ` [PATCH net-next v3 2/4] net: vhost: replace magic number of lock annotation xiangxia.m.yue
2018-07-02  2:21   ` Jason Wang
2018-06-30  6:33 ` xiangxia.m.yue
2018-06-30  6:33 ` [PATCH net-next v3 3/4] net: vhost: factor out busy polling logic to vhost_net_busy_poll() xiangxia.m.yue
2018-06-30  6:33 ` xiangxia.m.yue
2018-07-02  2:29   ` Jason Wang
2018-07-02  4:05     ` Tonghao Zhang
2018-06-30  6:33 ` [PATCH net-next v3 4/4] net: vhost: add rx busy polling in tx path xiangxia.m.yue
2018-06-30  6:33 ` xiangxia.m.yue
2018-06-30  7:03   ` Jesper Dangaard Brouer [this message]
2018-06-30  8:48     ` Tonghao Zhang
2018-07-02  2:32   ` Jason Wang

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=20180630090303.043a06c7@redhat.com \
    --to=brouer@redhat.com \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=xiangxia.m.yue@gmail.com \
    --cc=zhangtonghao@didichuxing.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 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.