On 11/08, Sameer Nanda wrote:
>
> @@ -413,12 +413,20 @@ void oom_kill_process(struct task_struct *p, gfp_t
> gfp_mask, int order,
> DEFAULT_RATELIMIT_BURST);
> @@ -456,10 +463,18 @@ void oom_kill_process(struct task_struct *p, gfp_t
> gfp_mask, int
On 11/08, Sameer Nanda wrote:
@@ -413,12 +413,20 @@ void oom_kill_process(struct task_struct *p, gfp_t
gfp_mask, int order,
DEFAULT_RATELIMIT_BURST);
@@ -456,10 +463,18 @@ void oom_kill_process(struct task_struct *p, gfp_t
gfp_mask, int order,
The selection of the process to be killed happens in two spots:
first in select_bad_process and then a further refinement by
looking for child processes in oom_kill_process. Since this is
a two step process, it is possible that the process selected by
select_bad_process may get a SIGKILL just
The selection of the process to be killed happens in two spots:
first in select_bad_process and then a further refinement by
looking for child processes in oom_kill_process. Since this is
a two step process, it is possible that the process selected by
select_bad_process may get a SIGKILL just
4 matches
Mail list logo