Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1558116

Re: [patch v2] mm, memcg: do not retry precharge charges

From Michal Hocko <mhocko@kernel.org>
Newsgroups linux.kernel
Subject Re: [patch v2] mm, memcg: do not retry precharge charges
Date 2017-01-13 09:50 +0100
Message-ID <sZ5IC-75W-9@gated-at.bofh.it> (permalink)
References <sYFl8-7QL-17@gated-at.bofh.it> <sYWlZ-1cO-27@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Thu 12-01-17 14:46:34, David Rientjes wrote:
> When memory.move_charge_at_immigrate is enabled and precharges are
> depleted during move, mem_cgroup_move_charge_pte_range() will attempt to
> increase the size of the precharge.
> 
> This can be allowed to do reclaim, but should not call the oom killer to
> oom kill a process.  It's better to fail the attach rather than oom kill
> a process attached to the memcg hierarchy.

This is not the case though since 3812c8c8f395 ("mm: memcg: do not trap
chargers with full callstack on OOM") - 3.12. Only the page fault path
is allowed to trigger the oom killer. 

> Prevent precharges from ever looping by setting __GFP_NORETRY.  This was
> probably the intention of the GFP_KERNEL & ~__GFP_NORETRY, which is
> pointless as written.
> 
> Fixes: 0029e19ebf84 ("mm: memcontrol: remove explicit OOM parameter in charge path")
> Signed-off-by: David Rientjes <rientjes@google.com>

Without the note about the oom killer you can add
Acked-by: Michal Hocko <mhocko@suse.com>

Thanks!

> ---
>  mm/memcontrol.c | 7 +++++--
>  1 file changed, 5 insertions(+), 2 deletions(-)
> 
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -4353,9 +4353,12 @@ static int mem_cgroup_do_precharge(unsigned long count)
>  		return ret;
>  	}
>  
> -	/* Try charges one by one with reclaim */
> +	/*
> +	 * Try charges one by one with reclaim, but do not retry.  This avoids
> +	 * calling the oom killer when the precharge should just fail.
> +	 */
>  	while (count--) {
> -		ret = try_charge(mc.to, GFP_KERNEL & ~__GFP_NORETRY, 1);
> +		ret = try_charge(mc.to, GFP_KERNEL | __GFP_NORETRY, 1);
>  		if (ret)
>  			return ret;
>  		mc.precharge++;

-- 
Michal Hocko
SUSE Labs

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[patch] mm, memcg: do not retry precharge charges David Rientjes <rientjes@google.com> - 2017-01-12 05:40 +0100
  Re: [patch] mm, memcg: do not retry precharge charges Michal Hocko <mhocko@kernel.org> - 2017-01-12 11:10 +0100
  Re: [patch] mm, memcg: do not retry precharge charges Michal Hocko <mhocko@kernel.org> - 2017-01-12 11:20 +0100
  [patch v2] mm, memcg: do not retry precharge charges David Rientjes <rientjes@google.com> - 2017-01-12 23:50 +0100
    Re: [patch v2] mm, memcg: do not retry precharge charges Michal Hocko <mhocko@kernel.org> - 2017-01-13 09:50 +0100
      Re: [patch v2] mm, memcg: do not retry precharge charges David Rientjes <rientjes@google.com> - 2017-01-13 11:20 +0100
        Re: [patch v2] mm, memcg: do not retry precharge charges Johannes Weiner <hannes@cmpxchg.org> - 2017-01-14 17:30 +0100
          Re: [patch v2] mm, memcg: do not retry precharge charges David Rientjes <rientjes@google.com> - 2017-01-15 06:50 +0100
            Re: [patch v2] mm, memcg: do not retry precharge charges Johannes Weiner <hannes@cmpxchg.org> - 2017-01-15 16:20 +0100
            Re: [patch v2] mm, memcg: do not retry precharge charges Michal Hocko <mhocko@kernel.org> - 2017-01-16 08:40 +0100

csiph-web