Lines Matching refs:space

26 occur.": that splits the virtual address space into 2 halves separated by a very
39 …0000000000000000 |    0       | 0000003fffffffff |  256 GB | user-space virtual memory, different …
47 …                                       | Kernel-space virtual memory, shared between all processes:
53    ffffffc800000000 | -224    GB | ffffffd7ffffffff |   64 GB | vmalloc/ioremap space
75 …0000000000000000 |    0       | 00007fffffffffff |  128 TB | user-space virtual memory, different …
83 …                                       | Kernel-space virtual memory, shared between all processes:
89    ffff8f8000000000 |  -112.5 TB | ffffaf7fffffffff |   32 TB | vmalloc/ioremap space
111 …0000000000000000 |   0        | 00ffffffffffffff |   64 PB | user-space virtual memory, different …
119 …                                       | Kernel-space virtual memory, shared between all processes:
125    ff20000000000000 | -56     PB | ff5fffffffffffff |   16 PB | vmalloc/ioremap space
140 To maintain compatibility with software that relies on the VA space with a
143 passing 0 into the hint address parameter of mmap. On CPUs with an address space
144 smaller than sv48, the CPU maximum supported address space will be the default.
146 Software can "opt-in" to receiving VAs from another VA space by providing
148 address space that fits entirely into the hint to be used, unless there is no
149 space left in the address space. If there is no space available in the requested
150 address space, an address in the next smallest available address space will be
153 For example, in order to obtain 48-bit VA space, a hint address greater than
156 kernel. Similarly, to obtain 57-bit VA space addresses, a hint address greater