Zach BrownandZach Brown ad99636af8 scoutfs: use scoutfs_key as btree key ...

The btree currently uses variable length big-endian buffers that are
compared with memcmp() as keys.  This is a historical relic of the time
when keys could be very large.  We had dirent keys that included the
name and manifest entries that included those fs keys.

But now all the btree callers are jumping through hoops to translate
their fs keys into big-endian btree keys.  And the memcmp() of the
keys is showing up in profiles.

This makes the btree take native scoutfs_key structs as its key.  The
forest callers which are working with fs keys can just pass their keys
straight through.  The server btree callers with their private btrees
get key fields definied for their use instead of having individual
big-endian key structs.

A nice side-effect of this is that splitting parents doesn't have to
assume that a maximal key will be inserted by a child split.  We can
have more keys in parents and wider trees.

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

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

kmod

scoutfs: use scoutfs_key as btree key

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

S

Description

No description provided

7.7 MiB

Languages

C 86.4%

Shell 10%

Roff 2.5%

TeX 0.8%

Makefile 0.3%