Repository navigation
Design: reorganize docs around subsystem architecture - #12
Merged
Merged
Conversation
Rewrite the design chapter as a continuous explanation of execution, filesystem, network and state paths. Add the VM, memory, filesystem, network and snapshot subsystem articles plus the records/versions and failure-semantics pages, and split the ADRs into separate files. Replace the daemon responsibility diagram in favor of the process ownership figure, and add SVGs for copy-up, apply conflicts, cold-page cycles, image reads, journal commits, memory COW and network paths. Fix macOS portability issues surfaced along the way: - Query Darwin peer identity with getpeereid so authorization no longer depends on a live peer PID. - Bounds-check the loaded Mach-O image header instead of reading through a libc struct. - Make mock S3 listeners blocking, since BSD/macOS can inherit the listener's nonblocking mode. - Gate Linux-only helpers and tests behind cfg(target_os = "linux"). - Rename fields and bindings to silence unused warnings. Enable CI and docs workflows on the next branch, and enlarge the sparse RAM copy test so the hole survives fsync on APFS.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rewrite the design chapter as a continuous explanation of execution, filesystem, network and state paths. Add the VM, memory, filesystem, network and snapshot subsystem articles plus the records/versions and failure-semantics pages, and split the ADRs into separate files.
Replace the daemon responsibility diagram in favor of the process ownership figure, and add SVGs for copy-up, apply conflicts, cold-page cycles, image reads, journal commits, memory COW and network paths.
Fix macOS portability issues surfaced along the way:
Enable CI and docs workflows on the next branch, and enlarge the sparse RAM copy test so the hole survives fsync on APFS.