Crate rotonda_store

A treebitmap based IP Prefix Store IP prefixes storage and retrieval data structures for IPv4 and IPv6 prefixes. This crate contains structures for both single and multi-threaded contexts, as well as async contexts.

The underlying tree structure is based on the tree bitmap as outlined in this paper.

Part of the Rotonda modular BGP engine. Read more about the data-structure in this blog post.

Re-exports

• pub use crossbeam_epoch as epoch;

Modules

• addr
  IP address resources.
• custom_alloc
• meta_examples
  Some simple metadata implementations
• prelude
• stats
  Statistics for the two trees (IPv4 and IPv6).

Structs

• Guard
  A guard that keeps the current thread pinned.
• MatchOptions
  The publicly available devices Options for the match_prefix method
• MultiThreadedStore
  A concurrently read/writable, lock-free Prefix Store, for use in a multi-threaded context.
• PrefixSingleRecordIter
  The publicly available devices
• PublicPrefixSingleRecord
• PublicRecord
• QueryResult
  The publicly available devices The type that is returned by a query.
• RecordSet
• RecordSingleSet
• SingleThreadedStore
  A fast, memory-efficient Prefix Store, for use in single-threaded contexts.
• Stats
  The publicly available devices
• Strides
  The publicly available devices

Enums

• MatchType
  The publicly available devices

Constants

• RECORDS_MAX_NUM
  The publicly available devices

Traits

• AddressFamily
  The address family of an IP address as a Trait.
• Meta
  Trait that describes how an existing record gets merged

Type Aliases

• IPv4
  Exactly fitting IPv4 bytes (4 octets).
• IPv6
  Exactly fitting IPv6 bytes (16 octets).