diff options
author | Vivek Goyal <vgoyal@redhat.com> | 2020-11-09 09:35:48 -0500 |
---|---|---|
committer | Dr. David Alan Gilbert <dgilbert@redhat.com> | 2020-12-18 10:08:24 +0000 |
commit | e49393a349925567cb83cfe810bc595e42a17883 (patch) | |
tree | f71b6aec0a26073e1210f34bcb29061fa988aa47 /tcg | |
parent | ff688cd2c7c3a677b71e4ea194a2fa49d07996c8 (diff) | |
download | qemu-e49393a349925567cb83cfe810bc595e42a17883.zip qemu-e49393a349925567cb83cfe810bc595e42a17883.tar.gz qemu-e49393a349925567cb83cfe810bc595e42a17883.tar.bz2 |
virtiofsd: Use --thread-pool-size=0 to mean no thread pool
Right now we create a thread pool and main thread hands over the request
to thread in thread pool to process. Number of threads in thread pool
can be managed by option --thread-pool-size.
In tests we have noted that many of the workloads are getting better
performance if we don't use a thread pool at all and process all
the requests in the context of a thread receiving the request.
Hence give user an option to be able to run virtiofsd without using
a thread pool.
To implement this, I have used existing option --thread-pool-size. This
option defines how many maximum threads can be in the thread pool.
Thread pool size zero freezes thead pool. I can't see why will one
start virtiofsd with a frozen thread pool (hence frozen file system).
So I am redefining --thread-pool-size=0 to mean, don't use a thread pool.
Instead process the request in the context of thread receiving request
from the queue.
Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
Message-Id: <20201109143548.GA1479853@redhat.com>
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Diffstat (limited to 'tcg')
0 files changed, 0 insertions, 0 deletions