Home
last modified time | relevance | path

Searched refs:_refcount (Results 1 – 7 of 7) sorted by relevance

/linux/mm/
H A Dzpdesc.h49 atomic_t _refcount; member
61 ZPDESC_MATCH(_refcount, _refcount);
H A Dslab.h140 SLAB_MATCH(_refcount, __page_refcount);
/linux/include/linux/
H A Dmm_types.h185 atomic_t _refcount; member
375 * @_refcount: Do not access this member directly. Use folio_ref_count()
435 atomic_t _refcount; member
521 FOLIO_MATCH(_refcount, _refcount);
538 FOLIO_MATCH(_refcount, _refcount_1);
622 TABLE_MATCH(_refcount, __page_refcount);
1853 * FOLL_PIN indicates that a special kind of tracking (not just page->_refcount,
/linux/drivers/iommu/
H A Diommu-pages.c19 IOPTDESC_MATCH(_refcount, __page_refcount);
/linux/include/net/
H A Dnetmem.h57 static_assert(sizeof(struct netmem_desc) <= offsetof(struct page, _refcount));
/linux/Documentation/core-api/
H A Dpin_user_pages.rst104 * Given the above, we can overload the page->_refcount field by using, sort of,
106 rather than dividing page->_refcount into bit fields, we simple add a medium-
108 page->_refcount. This provides fuzzy behavior: if a page has get_page() called
/linux/drivers/net/ethernet/cavium/thunder/
H A Dnicvf_queues.c170 prefetch(&page->_refcount); in nicvf_alloc_page()