Function report

Linux Kernel

v5.5.9

Brick Technologies Co., Ltd

Source Code:mm\page-writeback.c Create Date:2022-07-28 14:09:18
Last Modify:2022-05-23 13:25:58 Copyright©Brick
home page Tree
Annotation kernel can get tool activityDownload SCCTChinese

Name:global_dirtyable_memory - number of globally dirtyable pages* Return: the global number of pages potentially available for dirty* page cache. This is the base value for the global dirty limits.

Proto:static unsigned long global_dirtyable_memory(void)

Type:unsigned long

Parameter:Nothing

366  x = global_zone_page_state(NR_FREE_PAGES)
372  x -= min - return minimum of two values of the same or compatible types*@x: first value*@y: second value(x, linux/mm/page_alloc.c )
374  x += global_node_page_state(NR_INACTIVE_FILE)
375  x += global_node_page_state(NR_ACTIVE_FILE)
377  If Not highmem will not be subtracted from the total free memory* for calculating free ratios if vm_highmem_is_dirtyable is true Then x -= highmem_dirtyable_memory(x)
380  Return x + 1
Caller
NameDescribe
global_dirty_limitsglobal_dirty_limits - background-writeback and dirty-throttling thresholds*@pbackground: out parameter for bg_thresh*@pdirty: out parameter for thresh* Calculate bg_thresh and thresh for global_wb_domain. See* domain_dirty_limits() for details.
node_dirty_limitde_dirty_limit - maximum number of dirty pages allowed in a node*@pgdat: the node* Return: the maximum number of dirty pages allowed in a node, based* on the node's dirtyable memory.
balance_dirty_pagesalance_dirty_pages() must be called by processes which are generating dirty* data
wb_over_bg_threshwb_over_bg_thresh - does @wb need to be written back?*@wb: bdi_writeback of interest* Determines whether background writeback should keep writing @wb or it's* clean enough.* Return: %true if writeback should continue.