Lines Matching refs:kmap
58 This function should always be used, whereas kmap_atomic() and kmap() have
67 It's valid to take pagefaults in a local kmap region, unless the context
84 While it is significantly faster than kmap(), for the highmem case it
85 comes with restrictions about the pointers validity. Contrary to kmap()
92 therefore try to design their code to avoid the use of kmap() by mapping
128 * kmap(). This function has been deprecated; use kmap_local_page().
143 Mapping changes must be propagated across all the CPUs. kmap() also
144 requires global TLB invalidation when the kmap's pool wraps and it might
146 available. Therefore, kmap() is only callable from preemptible context.
151 kmap() is mostly wasted in such cases. kmap() was not intended for long
156 On 64-bit systems, calls to kmap_local_page(), kmap_atomic() and kmap() have