All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: virtualization@lists.linux-foundation.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	jasowang@redhat.com
Cc: mst@redhat.com, kvm@vger.kernel.org
Subject: [PATCH net-next V4 0/5] vhost: accelerate metadata access through vmap()
Date: Wed, 23 Jan 2019 17:55:52 +0800	[thread overview]
Message-ID: <20190123095557.30168-1-jasowang@redhat.com> (raw)

This series tries to access virtqueue metadata through kernel virtual
address instead of copy_user() friends since they had too much
overheads like checks, spec barriers or even hardware feature
toggling.

Test shows about 24% improvement on TX PPS. It should benefit other
cases as well.

Changes from V3:
- don't try to use vmap for file backed pages
- rebase to master
Changes from V2:
- fix buggy range overlapping check
- tear down MMU notifier during vhost ioctl to make sure invalidation
  request can read metadata userspace address and vq size without
  holding vq mutex.
Changes from V1:
- instead of pinning pages, use MMU notifier to invalidate vmaps and
  remap duing metadata prefetch
- fix build warning on MIPS

Jason Wang (5):
  vhost: generalize adding used elem
  vhost: fine grain userspace memory accessors
  vhost: rename vq_iotlb_prefetch() to vq_meta_prefetch()
  vhost: introduce helpers to get the size of metadata area
  vhost: access vq metadata through kernel virtual address

 drivers/vhost/net.c   |   4 +-
 drivers/vhost/vhost.c | 441 +++++++++++++++++++++++++++++++++++++-----
 drivers/vhost/vhost.h |  15 +-
 mm/shmem.c            |   1 +
 4 files changed, 410 insertions(+), 51 deletions(-)

-- 
2.17.1


             reply	other threads:[~2019-01-23  9:56 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-23  9:55 Jason Wang [this message]
2019-01-23  9:55 ` [PATCH net-next V4 1/5] vhost: generalize adding used elem Jason Wang
2019-01-23  9:55 ` Jason Wang
2019-01-23  9:55 ` [PATCH net-next V4 2/5] vhost: fine grain userspace memory accessors Jason Wang
2019-01-23  9:55 ` Jason Wang
2019-01-23  9:55 ` [PATCH net-next V4 3/5] vhost: rename vq_iotlb_prefetch() to vq_meta_prefetch() Jason Wang
2019-01-23  9:55 ` Jason Wang
2019-01-23  9:55 ` [PATCH net-next V4 4/5] vhost: introduce helpers to get the size of metadata area Jason Wang
2019-01-23  9:55 ` Jason Wang
2019-01-23  9:55 ` [PATCH net-next V4 5/5] vhost: access vq metadata through kernel virtual address Jason Wang
2019-01-23  9:55 ` Jason Wang
2019-01-23 14:08   ` Michael S. Tsirkin
2019-01-24  4:07     ` Jason Wang
2019-01-24  4:07       ` Jason Wang
2019-01-24  4:11       ` Jason Wang
2019-01-24  4:11         ` Jason Wang
2019-01-24  4:53         ` Michael S. Tsirkin
2019-01-24  4:53           ` Michael S. Tsirkin
2019-01-25  2:33           ` Jason Wang
2019-01-25  2:33           ` Jason Wang
2019-01-24  4:51       ` Michael S. Tsirkin
2019-01-24  4:51         ` Michael S. Tsirkin
2019-01-25  3:00       ` Michael S. Tsirkin
2019-01-25  3:00       ` Michael S. Tsirkin
2019-01-25  9:16         ` Jason Wang
2019-01-25  9:16         ` Jason Wang
2019-01-23 14:08   ` Michael S. Tsirkin
2019-01-25  3:03   ` Michael S. Tsirkin
2019-01-25  3:03     ` Michael S. Tsirkin
2019-01-25  9:21     ` Jason Wang
2019-01-25  9:21     ` Jason Wang
2019-01-25  9:24     ` Jason Wang
2019-01-25  9:24     ` Jason Wang
2019-01-23 13:58 ` [PATCH net-next V4 0/5] vhost: accelerate metadata access through vmap() Michael S. Tsirkin
2019-01-23 13:58 ` Michael S. Tsirkin
2019-01-23 17:24   ` David Miller
2019-01-23 17:24   ` David Miller
2019-01-26 22:37 ` David Miller
2019-01-26 22:37 ` David Miller
2019-01-27  0:31   ` Michael S. Tsirkin
2019-01-27  0:31   ` Michael S. Tsirkin
2019-01-29  2:34     ` Jason Wang
2019-01-29  2:34     ` Jason Wang
2019-01-23  9:55 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=20190123095557.30168-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 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.