Lines Matching refs:used

63 format is compatible with the format used in the first versions of the journal,
76 … siphash24 is used for newer journal files. For older files [Jenkins lookup3](https://en.wikipedia…
82 * Randomized, unique 128bit IDs are used in various locations. These are generally UUID v4 compatib…
103 ignored on reading. They are currently not used but might be used later on.
138 * An **ENTRY_ARRAY** object, which encapsulates a sorted array of offsets to entries, used for seek…
195 The currently used part of the file is the **header_size** plus the
227 table lookups, as the chains are traversed. This counter is used to determine
240 header's **compatible_flags** field. If a feature extension is used that makes
276 hash function the keyed siphash24 hash function is used for the two hash
322 performance. No file locking is used. The only time where disk synchronization
345 generated. Note that this is not used as a transaction scheme (it doesn't
410 **next_hash_offset** is used to link up DATA objects in the DATA_HASH_TABLE if
412 indicating the end). **next_field_offset** is used to link up data objects with
413 the same field name from the FIELD object of the field used.
442 Field objects are used to enumerate all possible values a certain field name
450 **next_hash_offset** is used to link up FIELD objects in the FIELD_HASH_TABLE
488 used hash function) the hash function used for this field, as singular
489 exception, is the Jenkins lookup3 hash function. The XOR hash value is used to
522 objects, respectively. DATA's and FIELD's next_hash_offset field are used to
555 Entry Arrays are used to store a sorted array of offsets to entries. Entry
592 Tag objects are used to seal off the journal for alteration. In regular
645 When interleaving multiple journal files seeking tends to be a frequently used
686 writing. Effectively, frequently used data objects should be in the memory
687 cache quickly. Non-frequently used data objects are likely to be located