Lines Matching full:mappings

89 of mappings.  Location differences are:
91 - For private mappings, the reservation map hangs off the VMA structure.
94 - For shared mappings, the reservation map hangs off the inode.  Specifically,
95   inode->i_mapping->private_data.  Since shared mappings are always backed
123 One of the big differences between PRIVATE and SHARED mappings is the way
126 - For shared mappings, an entry in the reservation map indicates a reservation
129 - For private mappings, the lack of an entry in the reservation map indicates
135 For private mappings, hugetlb_reserve_pages() creates the reservation map and
140 are needed for the current mapping/segment.  For private mappings, this is
141 always the value (to - from).  However, for shared mappings it is possible that
170 mappings, no modifications are made to the reservation map as lack of an
243 map.  For shared mappings where the reservation was present, an entry
266 to the page cache and pages in private mappings are added to an anonymous
337 Since shared mappings all point to and use the same underlying pages, the
338 biggest reservation concern for COW is private mappings.  In this case,
408 return value of region_chg().  However, in the case of shared mappings it is
445 private mappings, the lack of a entry in the reservation map indicates that
465 shared mappings and hide this detail from the caller::
503 different reservation map semantics for private and shared mappings.  Hence,
504 region_add is called for shared mappings (as an entry present in the map
505 indicates a reservation), and region_del is called for private mappings (as