From: xiangxia.m.yue@gmail.com
To: jasowang@redhat.com
Cc: netdev@vger.kernel.org,
virtualization@lists.linux-foundation.org, mst@redhat.com
Subject: [PATCH net-next v7 0/4] net: vhost: improve performance when enable busyloop
Date: Tue, 31 Jul 2018 20:00:50 -0700 [thread overview]
Message-ID: <1533092454-37196-1-git-send-email-xiangxia.m.yue@gmail.com> (raw)
From: Tonghao Zhang <xiangxia.m.yue@gmail.com>
This patches improve the guest receive performance.
On the handle_tx side, we poll the sock receive queue
at the same time. handle_rx do that in the same way.
For more performance report, see patch 4.
v6->v7:
fix issue and rebase codes:
1. on tx, busypoll will vhost_net_disable/enable_vq rx vq.
[This is suggested by Toshiaki Makita <makita.toshiaki@lab.ntt.co.jp>]
2. introduce common helper vhost_net_busy_poll_try_queue().
v5->v6:
rebase the codes.
Tonghao Zhang (4):
net: vhost: lock the vqs one by one
net: vhost: replace magic number of lock annotation
net: vhost: factor out busy polling logic to vhost_net_busy_poll()
net: vhost: add rx busy polling in tx path
drivers/vhost/net.c | 168 +++++++++++++++++++++++++++++++-------------------
drivers/vhost/vhost.c | 24 +++-----
2 files changed, 113 insertions(+), 79 deletions(-)
--
1.8.3.1
next reply other threads:[~2018-08-01 3:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 3:00 xiangxia.m.yue [this message]
2018-08-01 3:00 ` [PATCH net-next v7 1/4] net: vhost: lock the vqs one by one xiangxia.m.yue
2018-08-01 3:00 ` [PATCH net-next v7 2/4] net: vhost: replace magic number of lock annotation xiangxia.m.yue
2018-08-01 3:00 ` [PATCH net-next v7 3/4] net: vhost: factor out busy polling logic to vhost_net_busy_poll() xiangxia.m.yue
2018-08-01 3:00 ` [PATCH net-next v7 4/4] net: vhost: add rx busy polling in tx path xiangxia.m.yue
[not found] ` <1533092454-37196-4-git-send-email-xiangxia.m.yue@gmail.com>
2018-08-01 6:01 ` [PATCH net-next v7 3/4] net: vhost: factor out busy polling logic to vhost_net_busy_poll() Jason Wang
2018-08-01 9:52 ` Tonghao Zhang
2018-08-02 8:18 ` Jason Wang
[not found] ` <b4ffd376-6fa8-4d0c-5c3a-82d1b6e924d6@redhat.com>
2018-08-02 8:41 ` Toshiaki Makita
2018-08-02 9:23 ` Jason Wang
2018-08-02 9:57 ` Toshiaki Makita
2018-08-03 2:38 ` Jason Wang
2018-08-03 2:51 ` Tonghao Zhang
2018-08-03 3:07 ` Jason Wang
[not found] ` <CAMDZJNUMBYOVh+pzaykRq23ePqNR7BOA8wP_=i85-PXvwaxuBA@mail.gmail.com>
2018-08-03 3:07 ` Jason Wang
[not found] ` <fc4dc137-98de-2cee-4f41-e23ab4eb2492@redhat.com>
2018-08-03 3:24 ` Tonghao Zhang
[not found] ` <CAMDZJNWZ+WH3JhCy81h1VSka7-z2zF1Tw-EnLTr26J_5SkQZTg@mail.gmail.com>
2018-08-03 3:40 ` Toshiaki Makita
2018-08-03 4:14 ` Tonghao Zhang
[not found] ` <CAMDZJNUyZwcVpYc-3WGB_0CWSe-ti7c0BOvyFwwTo6PZ4s5V1Q@mail.gmail.com>
2018-08-03 4:25 ` Toshiaki Makita
2018-08-03 3:43 ` Jason Wang
[not found] ` <a900e9f3-3aad-2cfa-da4c-226bf8981059@redhat.com>
2018-08-03 4:04 ` Tonghao Zhang
2018-08-03 5:07 ` Jason Wang
2018-08-03 5:25 ` Toshiaki Makita
[not found] ` <90c0deec-6a7b-9787-b62f-7ea76a5cbd7c@redhat.com>
2018-08-03 3:32 ` Toshiaki Makita
2018-08-03 3:44 ` 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=1533092454-37196-1-git-send-email-xiangxia.m.yue@gmail.com \
--to=xiangxia.m.yue@gmail.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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