virtiofsd: Used glib "shared" thread pool
commit04d325e86f79bd61f8fd50d45ff795aca0dd3404
authorVivek Goyal <vgoyal@redhat.com>
Mon, 21 Sep 2020 21:32:16 +0000 (21 17:32 -0400)
committerDr. David Alan Gilbert <dgilbert@redhat.com>
Fri, 25 Sep 2020 11:45:58 +0000 (25 12:45 +0100)
tree5a2e459003c6a6a137de7f2032ebab7f282919bc
parentf1303afe222759105fc1787992098f5754c7e296
virtiofsd: Used glib "shared" thread pool

glib offers thread pools and it seems to support "exclusive" and "shared"
thread pools.

https://developer.gnome.org/glib/stable/glib-Thread-Pools.html#g-thread-pool-new

Currently we use "exlusive" thread pools but its performance seems to be
poor. I tried using "shared" thread pools and performance seems much
better. I posted performance results here.

https://www.redhat.com/archives/virtio-fs/2020-September/msg00080.html

So lets switch to shared thread pools. We can think of making it optional
once somebody can show in what cases exclusive thread pools offer better
results. For now, my simple performance tests across the board see
better results with shared thread pools.

Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
Message-Id: <20200921213216.GE13362@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
  With seccomp fix from Miklos
tools/virtiofsd/fuse_virtio.c
tools/virtiofsd/passthrough_seccomp.c