Searched refs:fullness (Results 1 – 5 of 5) sorted by relevance
264 unsigned int fullness:FULLNESS_BITS; member653 int fullness) in insert_zspage() argument655 class_stat_add(class, fullness, 1); in insert_zspage()656 list_add(&zspage->list, &class->fullness_list[fullness]); in insert_zspage()657 zspage->fullness = fullness; in insert_zspage()666 int fullness = zspage->fullness; in remove_zspage() local668 VM_BUG_ON(list_empty(&class->fullness_list[fullness])); in remove_zspage()671 class_stat_sub(class, fullness, 1); in remove_zspage()688 if (newfg == zspage->fullness) in fix_fullness_group()812 VM_BUG_ON(zspage->fullness != ZS_INUSE_RATIO_0); in __free_zspage()[all …]
137 Not that the count and fullness are not affected by clearing folios from the
90 "fullness group" which is calculated as the ratio of the "inuse" objects to
23 timestamps allow for applications to keep track of the 'fullness' of
2430 Buffer fullness