From: Stefan Hajnoczi <stefanha@redhat.com>
To: virtio-fs@redhat.com, qemu-devel@nongnu.org
Cc: Liu Bo <bo.liu@linux.alibaba.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: [Qemu-devel] [PATCH 0/4] virtiofsd: multithreading preparation part 3
Date: Thu, 1 Aug 2019 17:54:05 +0100 [thread overview]
Message-ID: <20190801165409.20121-1-stefanha@redhat.com> (raw)
This patch series introduces the virtiofsd --thread-pool-size=NUM and sets the
default value to 64. Each virtqueue has its own thread pool for processing
requests. Blocking requests no longer pause virtqueue processing and I/O
performance should be greatly improved when the queue depth is greater than 1.
Linux boot and pjdfstest have been tested with these patches and the default
thread pool size of 64.
I have now concluded the thread-safety code audit. Please let me know if you
have concerns about things I missed.
Performance
-----------
Please try these patches out and share your results.
Scalability
-----------
There are several synchronization primitives that are taken by the virtqueue
processing thread or the thread pool worker. Unfortunately this is necessary
to protect shared state. It means that thread pool workers contend on or at
least access thread synchronization primitives. If anyone has suggestions for
improving this situation, please discuss.
1. vu_dispatch_rwlock - libvhost-user from races between the vhost-user
protocol thread and the virtqueue processing and thread pool worker threads.
2. vq_lock - protects the virtqueue from races between the virtqueue processing
thread and thread pool workers.
3. init_rwlock - protects FUSE_INIT/FUSE_DESTROY from races with other
requests.
4. se->lock - protects se->list and the FUSE_INTERRUPT shared state.
Ideally we could avoid hitting all of these locks on each request. That would
make the code scale better.
Future work
-----------
This series does not complete the multithreading effort yet. Two items are
still missing:
1. Multiqueue support
2. CPU affinity for virtqueue processing threads and thread pools
Stefan Hajnoczi (4):
virtiofsd: process requests in a thread pool
virtiofsd: prevent FUSE_INIT/FUSE_DESTROY races
virtiofsd: fix lo_destroy() resource leaks
virtiofsd: add --thread-pool-size=NUM option
contrib/virtiofsd/fuse_i.h | 2 +
contrib/virtiofsd/fuse_lowlevel.c | 25 +-
contrib/virtiofsd/fuse_virtio.c | 491 ++++++++++++++++-------------
contrib/virtiofsd/passthrough_ll.c | 43 ++-
contrib/virtiofsd/seccomp.c | 1 +
5 files changed, 318 insertions(+), 244 deletions(-)
--
2.21.0
next reply other threads:[~2019-08-01 17:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 16:54 Stefan Hajnoczi [this message]
2019-08-01 16:54 ` [Qemu-devel] [PATCH 1/4] virtiofsd: process requests in a thread pool Stefan Hajnoczi
2019-08-05 12:02 ` Dr. David Alan Gilbert
2019-08-07 9:35 ` Stefan Hajnoczi
2019-08-01 16:54 ` [Qemu-devel] [PATCH 2/4] virtiofsd: prevent FUSE_INIT/FUSE_DESTROY races Stefan Hajnoczi
2019-08-05 12:26 ` Dr. David Alan Gilbert
2019-08-01 16:54 ` [Qemu-devel] [PATCH 3/4] virtiofsd: fix lo_destroy() resource leaks Stefan Hajnoczi
2019-08-05 15:17 ` Dr. David Alan Gilbert
2019-08-05 18:57 ` Dr. David Alan Gilbert
2019-08-06 18:58 ` Dr. David Alan Gilbert
2019-08-07 9:41 ` Stefan Hajnoczi
2019-08-01 16:54 ` [Qemu-devel] [PATCH 4/4] virtiofsd: add --thread-pool-size=NUM option Stefan Hajnoczi
2019-08-05 2:52 ` [Qemu-devel] [Virtio-fs] [PATCH 0/4] virtiofsd: multithreading preparation part 3 piaojun
2019-08-05 8:01 ` Stefan Hajnoczi
2019-08-05 9:40 ` piaojun
2019-08-07 18:03 ` [Qemu-devel] " Stefan Hajnoczi
2019-08-07 20:57 ` [Qemu-devel] [Virtio-fs] " Vivek Goyal
2019-08-08 9:02 ` Stefan Hajnoczi
2019-08-08 9:53 ` Dr. David Alan Gilbert
2019-08-08 12:53 ` Vivek Goyal
2019-08-09 8:23 ` Stefan Hajnoczi
2019-08-10 21:35 ` Liu Bo
2019-08-09 8:21 ` Stefan Hajnoczi
2019-08-10 21:34 ` Liu Bo
2019-08-11 2:26 ` piaojun
2019-08-12 10:05 ` Stefan Hajnoczi
2019-08-12 11:58 ` piaojun
2019-08-12 12:51 ` Dr. David Alan Gilbert
2019-08-08 8:10 ` piaojun
2019-08-08 9:53 ` Stefan Hajnoczi
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=20190801165409.20121-1-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=bo.liu@linux.alibaba.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=virtio-fs@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).