Lines Matching refs:pages

259      or not.  Note that several pages at once may be presented for marking.
261      The PG_fscache bit is set on the pages before this function would be
266 (10) A function to unmark all the pages retaining cache metadata [mandatory].
269      unbound from a cookie and that all the marks on the pages should be
271      its tracking information so that the pages don't need to be explicitly
433 Note that attempts to read or write data pages in the cache over this size may
445 And the sixth step is to store and retrieve pages in the cache.  There are
592 A facility is provided to read several pages at once, as requested by the
597 					struct list_head *pages,
605  (1) Any page it can retrieve data for is removed from pages and nr_pages and
606      dispatched for reading to the disk.  Reads of adjacent pages on disk may
609  (2) The mark_pages_cached() cookie operation will be called on several pages
614      Else if some pages couldn't be allocated or read, then -ENOBUFS will be
617      Else if some pages couldn't be read but were allocated, then -ENODATA will
620      Otherwise, if all pages had reads dispatched, then 0 will be returned, the
628 some of the pages being read and some being allocated.  Those pages will have
635 If one or more pages are passed to fscache_read_or_alloc_pages() but not then
637 those pages will need to have any marks and reservations removed.  This can be
641 				      struct list_head *pages);
644 fscache_read_or_alloc_pages().  Every page in the pages list will be examined
662 Note that pages can't be explicitly deleted from the a data file.  The whole
681 manage the heuristics of coping with vmscan trying to eject pages, which may
682 conflict with the cache trying to write pages to the cache (which may itself
702 A convenience routine is provided to perform an uncache on all the pages
703 attached to an inode.  This assumes that the pages on the inode correspond on a
704 1:1 basis with the pages in the cache.
709 This takes the netfs cookie that the pages were cached with and the inode that
710 the pages are attached to.  This function will wait for pages to finish being
748 invalidate its state; allocate, read or write backing pages - though it is
749 still possible to uncache pages and relinquish the cookie.
839 the cookies for "child" indices, objects and pages have been relinquished
900 after fscache_read_or_alloc_pages() as the former will try and release pages it