* [Virtio-fs] [virtiofsd] MR opened: Handle FUSE_INIT and FUSE_DESTROY non-concurrently
@ 2022-02-01 22:01 virtiofs-bot
0 siblings, 0 replies; only message in thread
From: virtiofs-bot @ 2022-02-01 22:01 UTC (permalink / raw)
To: virtio-fs
- Replace `futures::executor::ThreadPool` by `tokio::runtime::Runtime`.
This prepares for using tokio's implementation of `RwLock` with
owning lock guards that are `Send`, i.e., can be moved into other
threads.
- Handling FUSE_INIT or FUSE_DESTROY requests shouldn't be done
concurrently with handling some other request. To enforce this, we
require an exclusive reference (`&mut self`) when calling `init()`
or `destroy()` functions.
Furthermore, those requests (FUSE_INIT, FUSE_DESTROY) shouldn't be
reordered with other requests. To enforce this, we lock an `RwLock`
from the main thread and move the lock guard into the worker thread.
Locking from the main thread ensures that all previously queued
requests have already acquired their lock. This way, those requests
that require a write-lock (FUSE_INIT, FUSE_DESTROY) cannot be
reordered with requests that were enqueued earlier. For similar
reasons, they also cannot be reordered with requests that will be
enqueued later.
---
https://gitlab.com/virtio-fs/virtiofsd/-/merge_requests/85
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-02-01 22:01 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-02-01 22:01 [Virtio-fs] [virtiofsd] MR opened: Handle FUSE_INIT and FUSE_DESTROY non-concurrently virtiofs-bot
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.