Zach Brown 0820a7b5bd scoutfs: introduce write locking ...

Introduce the concept of acquiring write locks around write operations.

The core idea is that reads are unlocked and that write lock contention
between nodes should be rare.  This first pass simply broadcasts write
lock requests to all the mounts in the volume.  It achieves a reasonable
degree of fairness and doesn't require centralizing state in a lock
server.

We have to flesh out a bit of initial infrastructure to support the
write locking protocol.  The roster manages cluster membership and
messaging and only understands mounts in the same kernel for now.
Creation needs to know which inodes to try and lock so we see the start
of per-mount free inode reservations.

The transformation of users is straight forward: they aquire the write
lock on the inodes they're working with instead of holding a
transaction.  The write lock machinery now manages transactions.

This passes single mount testing but that isn't saying much.  The next
step is to run multi-mount tests.

Signed-off-by: Zach Brown <zab@versity.com>

2016-05-23 17:25:06 -07:00

..

src

scoutfs: introduce write locking

2016-05-23 17:25:06 -07:00

.gitignore

scoutfs: add cscope noise to .gitignore

2016-04-12 19:37:31 -07:00

Makefile

scoutfs: require sparse builds

2016-03-24 21:45:08 -07:00