From: Jason Wang <jasowang@redhat.com>
To: mst@redhat.com, virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, kvm@vger.kernel.org
Cc: wexu@redhat.com, stefanha@redhat.com
Subject: [PATCH net-next V5 0/3] vhost_net tx batching
Date: Wed, 18 Jan 2017 15:02:00 +0800 [thread overview]
Message-ID: <1484722923-7698-1-git-send-email-jasowang@redhat.com> (raw)
Hi:
This series tries to implement tx batching support for vhost. This was
done by using MSG_MORE as a hint for under layer socket. The backend
(e.g tap) can then batch the packets temporarily in a list and
submit it all once the number of bacthed exceeds a limitation.
Tests shows obvious improvement on guest pktgen over over
mlx4(noqueue) on host:
Mpps -+%
rx-frames = 0 0.91 +0%
rx-frames = 4 1.00 +9.8%
rx-frames = 8 1.00 +9.8%
rx-frames = 16 1.01 +10.9%
rx-frames = 32 1.07 +17.5%
rx-frames = 48 1.07 +17.5%
rx-frames = 64 1.08 +18.6%
rx-frames = 64 (no MSG_MORE) 0.91 +0%
Changes from V4:
- stick to NAPI_POLL_WEIGHT for rx-frames is user specify a value
greater than it.
Changes from V3:
- use ethtool instead of module parameter to control the maximum
number of batched packets
- avoid overhead when MSG_MORE were not set and no packet queued
Changes from V2:
- remove uselss queue limitation check (and we don't drop any packet now)
Changes from V1:
- drop NAPI handler since we don't use NAPI now
- fix the issues that may exceeds max pending of zerocopy
- more improvement on available buffer detection
- move the limitation of batched pacekts from vhost to tuntap
Please review.
Thanks
Jason Wang (3):
vhost: better detection of available buffers
vhost_net: tx batching
tun: rx batching
drivers/net/tun.c | 76 +++++++++++++++++++++++++++++++++++++++++++++++----
drivers/vhost/net.c | 23 ++++++++++++++--
drivers/vhost/vhost.c | 8 ++++--
3 files changed, 96 insertions(+), 11 deletions(-)
--
2.7.4
next reply other threads:[~2017-01-18 7:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 7:02 Jason Wang [this message]
2017-01-18 7:02 ` [PATCH net-next V5 1/3] vhost: better detection of available buffers Jason Wang
2017-01-18 17:03 ` Michael S. Tsirkin
2017-01-18 7:02 ` [PATCH net-next V5 2/3] vhost_net: tx batching Jason Wang
2017-01-18 17:03 ` Michael S. Tsirkin
2017-01-18 7:02 ` [PATCH net-next V5 3/3] tun: rx batching Jason Wang
2017-01-18 17:03 ` Michael S. Tsirkin
2017-01-18 21:35 ` [PATCH net-next V5 0/3] vhost_net tx batching David Miller
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=1484722923-7698-1-git-send-email-jasowang@redhat.com \
--to=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=wexu@redhat.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;
as well as URLs for NNTP newsgroup(s).