Function report

Linux Kernel

v5.5.9

Brick Technologies Co., Ltd

Source Code:mm\oom_kill.c Create Date:2022-07-28 14:05:45
Last Modify:2022-05-23 13:16:41 Copyright©Brick
home page Tree
Annotation kernel can get tool activityDownload SCCTChinese

Name:m_cpuset_eligible() - check task eligiblity for kill*@start: task struct of which task to consider*@oc: pointer to struct oom_control* Task eligibility is determined by whether or not a candidate task, @tsk,* shares the same mempolicy nodes as current if

Proto:static bool oom_cpuset_eligible(struct task_struct *start, struct oom_control *oc)

Type:bool

Parameter:

TypeParameterName
struct task_struct *start
struct oom_control *oc
89  bool ret = false
90  mask = Used to determine mempolicy
92  If is_memcg_oom(oc) Then Return true
95  _read_lock() - mark the beginning of an RCU read-side critical section* When synchronize_rcu() is invoked on one CPU while other CPUs* are within RCU read-side critical sections, then the* synchronize_rcu() is guaranteed to block until after all the other
96  for_each_thread(start, tsk)
97  If mask Then
104  ret = mempolicy_nodemask_intersects(tsk, mask)
105  Else
110  ret = cpuset_mems_allowed_intersects(current process, tsk)
112  If ret Then Break
115  _read_unlock() - marks the end of an RCU read-side critical section.* In most situations, rcu_read_unlock() is immune from deadlock.* However, in kernels built with CONFIG_RCU_BOOST, rcu_read_unlock()
117  Return ret
Caller
NameDescribe
oom_evaluate_task
dump_task
out_of_memory_of_memory - kill the "best" process when we run out of memory*@oc: pointer to struct oom_control* If we run out of memory, we have the choice between either* killing a random task (bad), letting the system crash (worse)