mirror of
https://github.com/versity/scoutfs.git
synced 2026-02-02 16:52:03 +00:00
scoutfs: remove MAX key TYPE and ZONE
These were used for constructing arrays of string mappings of key fields. We don't print keys with symbolic strings anymore so we don't need to maintain these values anymore. Signed-off-by: Zach Brown <zab@versity.com>
This commit is contained in:
@@ -348,7 +348,6 @@ struct scoutfs_bloom_block {
|
||||
#define SCOUTFS_RID_ZONE 3
|
||||
#define SCOUTFS_FS_ZONE 4
|
||||
#define SCOUTFS_LOCK_ZONE 5
|
||||
#define SCOUTFS_MAX_ZONE 8 /* power of 2 is efficient */
|
||||
|
||||
/* inode index zone */
|
||||
#define SCOUTFS_INODE_INDEX_META_SEQ_TYPE 1
|
||||
@@ -373,9 +372,6 @@ struct scoutfs_bloom_block {
|
||||
/* lock zone, only ever found in lock ranges, never in persistent items */
|
||||
#define SCOUTFS_RENAME_TYPE 1
|
||||
|
||||
#define SCOUTFS_MAX_TYPE 8 /* power of 2 is efficient */
|
||||
|
||||
|
||||
/*
|
||||
* The extents that map blocks in a fixed-size logical region of a file
|
||||
* are packed and stored in item values. The packed extents are
|
||||
|
||||
Reference in New Issue
Block a user