All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: xiangxia.m.yue@gmail.com
Cc: virtualization@lists.linux-foundation.org,
	netdev@vger.kernel.org,
	Tonghao Zhang <zhangtonghao@didichuxing.com>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH net-next v2] net: vhost: improve performance when enable busyloop
Date: Wed, 27 Jun 2018 22:24:43 +0800	[thread overview]
Message-ID: <369bea44-6ebd-337a-b20b-a28a604fa2e9@redhat.com> (raw)
In-Reply-To: <1529990276-61157-1-git-send-email-xiangxia.m.yue@gmail.com>



On 2018年06月26日 13:17, xiangxia.m.yue@gmail.com wrote:
> From: Tonghao Zhang <xiangxia.m.yue@gmail.com>
>
> This patch improves the guest receive performance from
> host. On the handle_tx side, we poll the sock receive
> queue at the same time. handle_rx do that in the same way.
>
> For avoiding deadlock, change the code to lock the vq one
> by one and use the VHOST_NET_VQ_XX as a subclass for
> mutex_lock_nested. With the patch, qemu can set differently
> the busyloop_timeout for rx or tx queue.
>
> We set the poll-us=100us and use the iperf3 to test
> its throughput. The iperf3 command is shown as below.
>
> on the guest:
> iperf3  -s -D
>
> on the host:
> iperf3  -c 192.168.1.100 -i 1 -P 10 -t 10 -M 1400
>
> * With the patch:     23.1 Gbits/sec
> * Without the patch:  12.7 Gbits/sec
>
> Signed-off-by: Tonghao Zhang <zhangtonghao@didichuxing.com>

Thanks a lot for the patch. Looks good generally, but please split this 
big patch into separate ones like:

patch 1: lock vqs one by one
patch 2: replace magic number of lock annotation
patch 3: factor out generic busy polling logic to vhost_net_busy_poll()
patch 4: add rx busy polling in tx path.

And please cc Michael in v3.

Thanks

  parent reply	other threads:[~2018-06-27 14:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-26  5:17 [PATCH net-next v2] net: vhost: improve performance when enable busyloop xiangxia.m.yue
2018-06-27 14:24 ` Jason Wang
2018-06-27 14:24 ` Jason Wang [this message]
2018-06-27 15:58   ` Michael S. Tsirkin
2018-06-28  4:40     ` Jason Wang
2018-06-28  4:40     ` Jason Wang
2018-06-28  6:44     ` Tonghao Zhang
2018-06-28  6:44     ` Tonghao Zhang
2018-06-27 15:58   ` Michael S. Tsirkin
2018-06-28  6:42   ` Tonghao Zhang

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=369bea44-6ebd-337a-b20b-a28a604fa2e9@redhat.com \
    --to=jasowang@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.