linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.cz>
To: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	linux-mm@kvack.org
Subject: Re: [patch 1/3] mm, oom: avoid looping when chosen thread detaches its mm
Date: Thu, 12 Jan 2012 15:26:38 +0100	[thread overview]
Message-ID: <20120112142638.GA1300@tiehlicka.suse.cz> (raw)
In-Reply-To: <alpine.DEB.2.00.1201111922500.3982@chino.kir.corp.google.com>

On Wed 11-01-12 19:24:20, David Rientjes wrote:
> oom_kill_task() returns non-zero iff the chosen process does not have any
> threads with an attached ->mm.
> 
> In such a case, it's better to just return to the page allocator and
> retry the allocation because memory could have been freed in the interim
> and the oom condition may no longer exist.  It's unnecessary to loop in
> the oom killer and find another thread to kill.
> 
> This allows both oom_kill_task() and oom_kill_process() to be converted
> to void functions.  If the oom condition persists, the oom killer will be
> recalled.
> 
> Signed-off-by: David Rientjes <rientjes@google.com>

Makes sense and the code is easier to read
Reviewed-by: Michal Hocko <mhocko@suse.cz>

Thanks
> ---
>  mm/oom_kill.c |   56 ++++++++++++++++++++------------------------------------
>  1 files changed, 20 insertions(+), 36 deletions(-)
> 
> diff --git a/mm/oom_kill.c b/mm/oom_kill.c
> --- a/mm/oom_kill.c
> +++ b/mm/oom_kill.c
> @@ -434,14 +434,14 @@ static void dump_header(struct task_struct *p, gfp_t gfp_mask, int order,
>  }
>  
>  #define K(x) ((x) << (PAGE_SHIFT-10))
> -static int oom_kill_task(struct task_struct *p, struct mem_cgroup *mem)
> +static void oom_kill_task(struct task_struct *p, struct mem_cgroup *mem)
>  {
>  	struct task_struct *q;
>  	struct mm_struct *mm;
>  
>  	p = find_lock_task_mm(p);
>  	if (!p)
> -		return 1;
> +		return;
>  
>  	/* mm cannot be safely dereferenced after task_unlock(p) */
>  	mm = p->mm;
> @@ -477,15 +477,13 @@ static int oom_kill_task(struct task_struct *p, struct mem_cgroup *mem)
>  
>  	set_tsk_thread_flag(p, TIF_MEMDIE);
>  	force_sig(SIGKILL, p);
> -
> -	return 0;
>  }
>  #undef K
>  
> -static int oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order,
> -			    unsigned int points, unsigned long totalpages,
> -			    struct mem_cgroup *mem, nodemask_t *nodemask,
> -			    const char *message)
> +static void oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order,
> +			     unsigned int points, unsigned long totalpages,
> +			     struct mem_cgroup *mem, nodemask_t *nodemask,
> +			     const char *message)
>  {
>  	struct task_struct *victim = p;
>  	struct task_struct *child;
> @@ -501,7 +499,7 @@ static int oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order,
>  	 */
>  	if (p->flags & PF_EXITING) {
>  		set_tsk_thread_flag(p, TIF_MEMDIE);
> -		return 0;
> +		return;
>  	}
>  
>  	task_lock(p);
> @@ -533,7 +531,7 @@ static int oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order,
>  		}
>  	} while_each_thread(p, t);
>  
> -	return oom_kill_task(victim, mem);
> +	oom_kill_task(victim, mem);
>  }
>  
>  /*
> @@ -580,15 +578,10 @@ void mem_cgroup_out_of_memory(struct mem_cgroup *mem, gfp_t gfp_mask)
>  	check_panic_on_oom(CONSTRAINT_MEMCG, gfp_mask, 0, NULL);
>  	limit = mem_cgroup_get_limit(mem) >> PAGE_SHIFT;
>  	read_lock(&tasklist_lock);
> -retry:
>  	p = select_bad_process(&points, limit, mem, NULL);
> -	if (!p || PTR_ERR(p) == -1UL)
> -		goto out;
> -
> -	if (oom_kill_process(p, gfp_mask, 0, points, limit, mem, NULL,
> -				"Memory cgroup out of memory"))
> -		goto retry;
> -out:
> +	if (p && PTR_ERR(p) != -1UL)
> +		oom_kill_process(p, gfp_mask, 0, points, limit, mem, NULL,
> +				 "Memory cgroup out of memory");
>  	read_unlock(&tasklist_lock);
>  }
>  #endif
> @@ -745,33 +738,24 @@ void out_of_memory(struct zonelist *zonelist, gfp_t gfp_mask,
>  	if (sysctl_oom_kill_allocating_task &&
>  	    !oom_unkillable_task(current, NULL, nodemask) &&
>  	    current->mm) {
> -		/*
> -		 * oom_kill_process() needs tasklist_lock held.  If it returns
> -		 * non-zero, current could not be killed so we must fallback to
> -		 * the tasklist scan.
> -		 */
> -		if (!oom_kill_process(current, gfp_mask, order, 0, totalpages,
> -				NULL, nodemask,
> -				"Out of memory (oom_kill_allocating_task)"))
> -			goto out;
> +		oom_kill_process(current, gfp_mask, order, 0, totalpages, NULL,
> +				 nodemask,
> +				 "Out of memory (oom_kill_allocating_task)");
> +		goto out;
>  	}
>  
> -retry:
>  	p = select_bad_process(&points, totalpages, NULL, mpol_mask);
> -	if (PTR_ERR(p) == -1UL)
> -		goto out;
> -
>  	/* Found nothing?!?! Either we hang forever, or we panic. */
>  	if (!p) {
>  		dump_header(NULL, gfp_mask, order, NULL, mpol_mask);
>  		read_unlock(&tasklist_lock);
>  		panic("Out of memory and no killable processes...\n");
>  	}
> -
> -	if (oom_kill_process(p, gfp_mask, order, points, totalpages, NULL,
> -				nodemask, "Out of memory"))
> -		goto retry;
> -	killed = 1;
> +	if (PTR_ERR(p) != -1UL) {
> +		oom_kill_process(p, gfp_mask, order, points, totalpages, NULL,
> +				 nodemask, "Out of memory");
> +		killed = 1;
> +	}
>  out:
>  	read_unlock(&tasklist_lock);
>  
> 
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@kvack.org.  For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
> Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

-- 
Michal Hocko
SUSE Labs
SUSE LINUX s.r.o.
Lihovarska 1060/12
190 00 Praha 9    
Czech Republic

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2012-01-12 14:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-12  3:24 [patch 1/3] mm, oom: avoid looping when chosen thread detaches its mm David Rientjes
2012-01-12  3:24 ` [patch 2/3] mm, oom: fold oom_kill_task into oom_kill_process David Rientjes
2012-01-12  3:48   ` KOSAKI Motohiro
2012-01-12  4:48   ` KAMEZAWA Hiroyuki
2012-01-12  3:24 ` [patch 3/3] mm, oom: do not emit oom killer warning if chosen thread is already exiting David Rientjes
2012-01-12  3:48   ` KOSAKI Motohiro
2012-01-12  4:49   ` KAMEZAWA Hiroyuki
2012-01-12 14:44   ` Michal Hocko
2012-01-12  4:47 ` [patch 1/3] mm, oom: avoid looping when chosen thread detaches its mm KAMEZAWA Hiroyuki
2012-01-12 14:26 ` Michal Hocko [this message]
2012-01-14  0:39 ` [patch -mm " David Rientjes
2012-01-14  0:39   ` [patch -mm 2/3] mm, oom: fold oom_kill_task into oom_kill_process David Rientjes
2012-01-14  0:39   ` [patch -mm 3/3] mm, oom: do not emit oom killer warning if chosen thread is already exiting David Rientjes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120112142638.GA1300@tiehlicka.suse.cz \
    --to=mhocko@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=rientjes@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).