Design 47 H: H-A-292, a module's own tool may read its own state in one page
This commit is contained in:
@@ -1688,3 +1688,10 @@ Where two preparers disagreed, the chosen one is named.
|
||||
a start asks a publish again only for each module's newest such reservation (H-A-275: the older digest is dead).
|
||||
(2) When a live publish is enqueued while a pass sends a start list, the pass finishes the sends in flight and
|
||||
lists again, so the live one goes next; a pass never relists for a start-class enqueue. P3, H-A-275, H-A-290.
|
||||
- **H-A-292 (a module's own tool may read its own state in one page, 18:54)** Amends H-A-255 (2) for one case: a
|
||||
module's read tool that answers about one of the module's own states (the builder's publish queue, its acted and
|
||||
re-ask states) may read that state in pages when one page of about 768 KB holds the whole state, so a call costs
|
||||
one replay of the bucket instead of one request per key; a state a page cannot hold is still not read in pages in
|
||||
H1 (H-A-255's "pages by sequence" stays owed, H2). Not for another module's state (ADR 0596). P7, tools-are-how-a-
|
||||
module-is-spoken-to. Also, H-A-291 (1) note: a module with two standing series (two MAJOR.MINOR catalog entries) is
|
||||
not retired across series; none exists today (43 reservations, one series each).
|
||||
|
||||
Reference in New Issue
Block a user