Function report

Linux Kernel

v5.5.9

Brick Technologies Co., Ltd

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

Name:de_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.

Proto:static unsigned long node_dirty_limit(struct pglist_data *pgdat)

Type:unsigned long

Parameter:

TypeParameterName
struct pglist_data *pgdat
479  node_memory = de_dirtyable_memory - number of dirtyable pages in a node*@pgdat: the node* Return: the node's number of pages potentially available for dirty* page cache. This is the base value for the per-node dirty limits.
480  tsk = current process
483  If vm_dirty_bytes starts at 0 (disabled) so that it is a function of* vm_dirty_ratio * the amount of dirtyable memory Then dirty = DIV_ROUND_UP(vm_dirty_bytes starts at 0 (disabled) so that it is a function of* vm_dirty_ratio * the amount of dirtyable memory, PAGE_SIZE) * node_memory / 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.
486  Else dirty = The generator of dirty data starts writeback at this percentage * node_memory / 100
489  If flags & Throttle me less: I clean memory || rt_task(tsk) Then dirty += dirty / 4
492  Return dirty
Caller
NameDescribe
node_dirty_okde_dirty_ok - tells whether a node is within its dirty limits*@pgdat: the node to check* Return: %true when the dirty pages in @pgdat are within the node's* dirty limit, %false if the limit is exceeded.