Zach Brown 6bacd95aea scoutfs: fs uses item cache instead of forest ...

Use the new item cache for all the item work in the fs instead of
calling into the forest of btrees.  Most of this is mechanical
conversion from the _forest calls to the _item calls.  The item cache
no longer supports the kvec argument for describing values so all the
callers pass in the value pointer and length directly.

The item cache doesn't support saving items as they're deleted and later
restoring them from an error unwinding path.  There were only two users
of this.  Directory entries can easily guarantee that deletion won't
fail by dirtying the items first in the item cache.  Xattr updates were
a little trickier.  They can combine dirtying, creating, updating, and
deleting to atomically switch between items that describe different
versions of a multi-item value.  This also fixed a bug in the srch
xattrs where replacing an xattr would create a new id for the xattr and
leave existing srch items referencing a now deleted id.  Replacing now
reuses the old id.

And finally we add back in the locking and transaction item cache
integration.

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

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

kmod

scoutfs: fs uses item cache instead of forest

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

Description

No description provided

7.1 MiB

Languages

C 87.1%

Shell 9.2%

Roff 2.5%

TeX 0.9%

Makefile 0.3%