From: Jason Wang <jasowang@redhat.com>
To: mst@redhat.com, jasowang@redhat.com
Cc: kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH net-next V2 0/3] basic in order support for vhost_net
Date: Wed, 9 Jan 2019 16:05:27 +0800 [thread overview]
Message-ID: <20190109080530.18572-1-jasowang@redhat.com> (raw)
Hi:
This series implement basic in order feature support for
vhost_net. This feature requires both driver and device to use
descriptors in order which can simplify the implementation and
optimizaton for both side. The series also implement a simple
optimization that avoid read available ring. Test shows 10%
performance improvement at most.
More optimizations could be done on top.
Changes from V1:
- no code changes
- add result of SMAP off
Jason Wang (3):
virtio: introduce in order feature bit
vhost_net: support in order feature
vhost: don't touch avail ring if in_order is negotiated
drivers/vhost/net.c | 6 ++++--
drivers/vhost/vhost.c | 19 ++++++++++++-------
include/uapi/linux/virtio_config.h | 6 ++++++
3 files changed, 22 insertions(+), 9 deletions(-)
--
2.17.1
next reply other threads:[~2019-01-09 8:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 8:05 Jason Wang [this message]
2019-01-09 8:05 ` [PATCH net-next V2 1/3] virtio: introduce in order feature bit Jason Wang
2019-01-09 14:27 ` Michael S. Tsirkin
2019-01-09 8:05 ` [PATCH net-next V2 2/3] vhost_net: support in order feature Jason Wang
2019-01-09 8:05 ` [PATCH net-next V2 3/3] vhost: don't touch avail ring if in_order is negotiated Jason Wang
2019-01-09 12:19 ` [PATCH net-next V2 0/3] basic in order support for vhost_net 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=20190109080530.18572-1-jasowang@redhat.com \
--to=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).