Lines Matching full:pages

35 In other words, use pin_user_pages*() for DMA-pinned pages, and
40 multiple threads and call sites are free to pin the same struct pages, via both
55 pages* array, and the function then pins pages by incrementing each by a special
58 For huge pages (and in fact, any compound page of more than 2 pages), the
63 This approach for compound pages avoids the counting upper limit problems that
65 huge pages, because each tail page adds a refcount to the head page. And in
69 This also means that huge pages and compound pages (of order > 1) do not suffer
80 but the caller passed in a non-null struct pages* array, then the function
81 sets FOLL_GET for you, and proceeds to pin pages by incrementing the refcount
90 Tracking dma-pinned pages
94 pages:
116 * Callers must specifically request "dma-pinned tracking of pages". In other
128 There are GUP references to pages that are serving
140 There are GUP references to pages that are serving as DMA
147 NOTE: Some pages, such as DAX pages, cannot be pinned with longterm pins. That's
148 because DAX pages do not have a separate page cache, and so "pinning" implies
153 Device drivers can pin pages via get_user_pages*(), and register for mmu
156 the pages. There may be other possible schemes, such as for example explicitly
164 Either way, as long as the driver unpins the pages upon mmu notifier callback,
184     write to the data within the pages
189     write to the data within the pages
195 The whole point of marking pages as "DMA-pinned" or "gup-pinned" is to be able
215 short term pins on pages whose data *will* get accessed. As such, FOLL_PIN is
217 restrictive case that has FOLL_PIN as a prerequisite: this is for pages that
231 You can monitor how many total dma-pinned pages have been acquired and released
241   acquired since the system was powered on. For huge pages, the head page is
244   pages: the head page is refcounted once for each tail or head page in the huge
248   the system was powered on. Note that pages are released (unpinned) on a
268 to better report on compound pages in general. Specifically, for compound pages