Lines Matching full:mappings

87 of mappings.  Location differences are:
89 - For private mappings, the reservation map hangs off the VMA structure.
92 - For shared mappings, the reservation map hangs off the inode.  Specifically,
93   inode->i_mapping->private_data.  Since shared mappings are always backed
121 One of the big differences between PRIVATE and SHARED mappings is the way
124 - For shared mappings, an entry in the reservation map indicates a reservation
127 - For private mappings, the lack of an entry in the reservation map indicates
133 For private mappings, hugetlb_reserve_pages() creates the reservation map and
138 are needed for the current mapping/segment.  For private mappings, this is
139 always the value (to - from).  However, for shared mappings it is possible that
168 mappings, no modifications are made to the reservation map as lack of an
242 map.  For shared mappings where the reservation was present, an entry
265 to the page cache and pages in private mappings are added to an anonymous
336 Since shared mappings all point to and use the same underlying pages, the
337 biggest reservation concern for COW is private mappings.  In this case,
407 return value of region_chg().  However, in the case of shared mappings it is
444 private mappings, the lack of a entry in the reservation map indicates that
464 shared mappings and hide this detail from the caller::
502 different reservation map semantics for private and shared mappings.  Hence,
503 region_add is called for shared mappings (as an entry present in the map
504 indicates a reservation), and region_del is called for private mappings (as