Zach Brown ca6b7f1e6d scoutfs: lock invalidate only syncs dirty ...

Lock invalidation has to make sure that changes are visible to future
readers.  It was syncing if the current transaction is dirty.  This was
never optimal, but it wasn't catastrophic when concurrent invalidation
work could all block on one sync in progress.

With the move to a single invalidation worker serially invalidating
locks it became unacceptable.  Invalidation happening in the presence of
writers would constantly sync the current transaction while very old
unused write locks were invalidated.  Their changes had long since been
committed in previous transactions.

We add a lock field to remember the transaction sequence which could
have been dirtied under the lock.  If that transaction has already been
comitted by the time we invalidate the lock it doesn't have to sync.

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

2020-08-26 14:39:12 -07:00

kmod

scoutfs: lock invalidate only syncs dirty

2020-08-26 14:39:12 -07:00

Description

No description provided

6 MiB

Languages

C 86.4%

Shell 10%

Roff 2.5%

TeX 0.8%

Makefile 0.3%