Lines Matching refs:that

26 exceeds the maximum size of virtual memory.  At that point it becomes
29 the pieces of physical memory that it wants to access.
33 where exactly that border lies.
36 VM space so that we don't have to pay the full TLB invalidation costs for
51 This means that the kernel can at most map 1GiB of physical memory at any one
56 Other architectures that have mm context tagged TLBs can have separate kernel
77      page.  Since the mapping is restricted to the CPU that issued it, it
78      performs well, but the issuing task is therefore required to stay on that
84      It may be assumed that k[un]map_atomic() won't fail.
92 wants to access the contents of a page that might be allocated from high memory
99 	/* Gain access to the contents of that page. */
102 	/* Do something to the contents of that page. */
105 	/* Unmap that page. */
108 Note that the kunmap_atomic() call takes the result of the kmap_atomic() call
131 simply with a bit of arithmetic that will convert the page struct address into
150      page being 32-bytes that would end up being something in the order of 112G
152      page-frames in that memory...
156      advantage is that PAE has more PTE bits and can provide advanced features
159 The general recommendation is that you don't use more than 8GiB on a 32-bit