diff options
Diffstat (limited to 'design/README.md')
| -rw-r--r-- | design/README.md | 42 |
1 files changed, 17 insertions, 25 deletions
diff --git a/design/README.md b/design/README.md index f9bdf35..dcaaf37 100644 --- a/design/README.md +++ b/design/README.md @@ -1321,34 +1321,26 @@ What stays, and why: ### segments -The address space, the textbook's picture: one tall rectangle, high -addresses on top (the stack at the top growing down, the heap growing up), -the mapped parts as bands in their inks (55% toward the page), the holes -between them broken. It is where the inks come from. +The address space to true scale, for its physicality, then magnified +until its parts can be named (the powers of ten). High addresses on top, +as the textbook draws it; 0 at the foot. -| Part | Drawn | +| Level | Drawn | | --- | --- | -| the rectangle | 140 wide; `ffffffffffffffff` over it and `0` under it, faint | -| a band | a mapping: its ink as fill, a 2-unit page line at its top so a file's mappings read as parts of one thing; 24 high at least and 4 more a doubling past 4 KiB (1.5 MiB is 58): schematic, by the logarithm of its size, and its title says `not to scale` | -| a hole | what is not mapped: a fixed 40, two zig-zags across it, its size beside it (`nothing mapped · 127 TiB`; `15 EiB` above the stack) | -| its labels | outside, so the bands stay clean: on the left the band's first address in its ink, at the band's foot; on the right, after a 2-unit leader, its permissions in its ink, what it is (code, read-only, data, data (anonymous), `[stack]`, `[heap]`, `[vdso]`), its size | -| a file's parts | a bracket right of the labels spanning its bands, the file's name beside it (`libc.so.6`: r--, r-x, r--, r--, rw-) | -| growth | a 2-unit `bright` arrow in the stack's band pointing down, in the heap's pointing up | -| live | rsp's and rip's pins at their place in their bands; a band framed as read (3 units) when a word is inked into it; the heap's top glides when `brk` grows it (12 f); a new mapping fades into its hole (12 f), the hole closing round it | - -**Orientation.** High addresses on top, against every panel of the -language, which keeps low addresses on top. The rectangle is the whole -space at once, read as the textbook draws it, as the user asked; the -panels are rows of memory read like text. The introduction says it once, -in the beat that sets the stack panel beside the rectangle: the stack -grows down the rectangle and up its panel, the same pushes; the growth -arrows carry it. +| the whole | a rectangle 60 wide, the user half, 0 to 0x7fffffffffff (128 TiB), linear, a ruler every 16 TiB on its left; above its top, faint, `16 EiB not canonical, then the kernel's half` (to scale they would make the user half 1/131 072 of the bar). Every mapping where it is, at least a 1-unit hairline in its ink: at this scale that is all they are, and that is the point. No text in it but the ruler | +| a magnification | a second rectangle beside, joined to the stretch it enlarges by the two lines of the magnification (2, `rule`), its own linear ruler, its factor over it (`the top 256 MiB · × 500 000`). Two clusters, two magnifications: the top (the libraries and the stack) and the bottom 20 MiB (the program and its heap); a third where a cluster still crowds (`the libraries, 4 MiB · × 32`) | +| names | only at the level where a band is 6 tall or more: a leader, permissions, the file or `[stack]`, the size. A file's mappings touch, its parts split by a page line. What stays a hairline even magnified (the stack, 132 KiB) is named by a leader to empty page | +| live | rsp and rip pinned at the level that names their band; a band framed as read when a word is inked into it; growth arrows in the stack (down) and the heap (up); `brk` and `mmap` as before | -**Where it lives.** The introduction (mock 30), the map's key, the title -card's legend. In the working frame it has no standing place (the -registers' tag carries its inks in short); a scene about memory layout can -take it as its drawing (`brk`, `mmap`), its view the mappings as rows. -Mocks 30 and 34. +It is the `loupe` for addresses: a place enlarged beside where it is, +tied to it; levels in depth instead of pointers. In motion it is a real +zoom: the camera goes into the whole along the magnification lines, the +ruler's unit changing as it passes (TiB to MiB to KiB), 72 f a level, +`glide`, and the insets are its resting pictures. The caption gives the +scale as a body: if the space were as tall as the Eiffel Tower, all the +program maps would be thinner than a hair, the stack a third of a micron. +Mocks 30, 34, and 35 (three treatments: A this, B one strip of levels +left to right, C true scale alone with distances written). ### aligned |
