Lines Matching refs:space
13 from the top of the 64-bit address space. It's easier to understand the layout
17 64-bit address space (ffffffffffffffff).
19 Note that as we get closer to the top of the address space, the notation changes
24 It also shows it nicely how incredibly large 64-bit address space is.
32 …0000000000000000 | 0 | 00007fffffffffff | 128 TB | user-space virtual memory, different …
40 … | Kernel-space virtual memory, shared between all processes:
47 ffffc90000000000 | -55 TB | ffffe8ffffffffff | 32 TB | vmalloc/ioremap space (vmalloc_base)
63 ffffffef00000000 | -68 GB | fffffffeffffffff | 64 GB | EFI region mapping space
67 ffffffffa0000000 |-1536 MB | fffffffffeffffff | 1520 MB | module mapping space
80 - With 56-bit addresses, user-space memory gets expanded by a factor of 512x,
91 …0000000000000000 | 0 | 00ffffffffffffff | 64 PB | user-space virtual memory, different …
99 … | Kernel-space virtual memory, shared between all processes:
106 ffa0000000000000 | -24 PB | ffd1ffffffffffff | 12.5 PB | vmalloc/ioremap space (vmalloc_base)
122 ffffffef00000000 | -68 GB | fffffffeffffffff | 64 GB | EFI region mapping space
126 ffffffffa0000000 |-1536 MB | fffffffffeffffff | 1520 MB | module mapping space
136 This causes hole between user space and kernel addresses if you interpret them
143 vmalloc space is lazily synchronized into the different PML4/PML5 pages of
153 physical memory, vmalloc/ioremap space and virtual memory map are randomized.