Expand description
The extension table client (blueprint §9.1’s ext_store/load/drop, §7.3).
A small key/value store the daemon keeps on a node’s behalf, and the seam through which pinned host buffers and accelerator IPC handles will reach a node in 0.2 (§7.3 “extension & pinned-memory”). What makes it worth having now is what it survives: an entry outlives the node that stored it, so a restarted node can pick up a calibration, a warm cache or a device handle that its previous incarnation left behind.
§Namespacing
ExtensionKey is namespace/name, and a node may only write the user
namespace (ExtensionKey::is_writable_by_node). The reserved ones are
the daemon’s to fill: a node reads the pinned buffer it was granted, it
does not invent one. Node::ext_store refuses a reserved key locally
rather than making a round trip to be told no.
§Time to live
Node::ext_store_with_ttl sets one. Without it a crashed node’s handles
accumulate, which is the whole reason the wire carries a ttl field.
§Reads are a round trip
ExtLoad is answered by an ExtValue event, which the session dispatcher
routes to the caller rather than to the node’s stream. That makes
Node::ext_load a blocking call with a deadline — and gives it an async
twin for a node whose loop is already asynchronous.
Functions§
- is_
writable - Whether a namespace is one a node may write (§7.3).