All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: David Rientjes <rientjes@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Michal Hocko <mhocko@suse.cz>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	linux-mm@kvack.org, cgroups@vger.kernel.org,
	linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 1/2] arch: invoke oom-killer from page fault
Date: Thu, 6 Jun 2013 12:19:29 +0530	[thread overview]
Message-ID: <51B030F9.4080804@synopsys.com> (raw)
In-Reply-To: <20130606043620.GA9406@cmpxchg.org>

On 06/06/2013 10:06 AM, Johannes Weiner wrote:
> From: Johannes Weiner <hannes@cmpxchg.org>
> Subject: [patch] mm: invoke oom-killer from remaining unconverted page fault
>  handlers
> 
> A few remaining architectures directly kill the page faulting task in
> an out of memory situation.  This is usually not a good idea since
> that task might not even use a significant amount of memory and so may
> not be the optimal victim to resolve the situation.
> 
> Since '1c0fe6e mm: invoke oom-killer from page fault' (2.6.29) there
> is a hook that architecture page fault handlers are supposed to call
> to invoke the OOM killer and let it pick the right task to kill.
> Convert the remaining architectures over to this hook.
> 
> To have the previous behavior of simply taking out the faulting task
> the vm.oom_kill_allocating_task sysctl can be set to 1.
> 
> Signed-off-by: Johannes Weiner <hannes@cmpxchg.org>

Acked-by: Vineet Gupta <vgupta@synopsys.com>   # for arch/arc bits

--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: David Rientjes <rientjes@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Michal Hocko <mhocko@suse.cz>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	linux-mm@kvack.org, cgroups@vger.kernel.org,
	linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 1/2] arch: invoke oom-killer from page fault
Date: Thu, 6 Jun 2013 12:19:29 +0530	[thread overview]
Message-ID: <51B030F9.4080804@synopsys.com> (raw)
Message-ID: <20130606064929.K-rh424k-o9frzti8iKGD8eFCLyO8hzg5YiVsYowuww@z> (raw)
In-Reply-To: <20130606043620.GA9406@cmpxchg.org>

On 06/06/2013 10:06 AM, Johannes Weiner wrote:
> From: Johannes Weiner <hannes@cmpxchg.org>
> Subject: [patch] mm: invoke oom-killer from remaining unconverted page fault
>  handlers
> 
> A few remaining architectures directly kill the page faulting task in
> an out of memory situation.  This is usually not a good idea since
> that task might not even use a significant amount of memory and so may
> not be the optimal victim to resolve the situation.
> 
> Since '1c0fe6e mm: invoke oom-killer from page fault' (2.6.29) there
> is a hook that architecture page fault handlers are supposed to call
> to invoke the OOM killer and let it pick the right task to kill.
> Convert the remaining architectures over to this hook.
> 
> To have the previous behavior of simply taking out the faulting task
> the vm.oom_kill_allocating_task sysctl can be set to 1.
> 
> Signed-off-by: Johannes Weiner <hannes@cmpxchg.org>

Acked-by: Vineet Gupta <vgupta@synopsys.com>   # for arch/arc bits

WARNING: multiple messages have this Message-ID (diff)
From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: David Rientjes <rientjes@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Michal Hocko <mhocko@suse.cz>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	<linux-mm@kvack.org>, <cgroups@vger.kernel.org>,
	<linux-arch@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [patch 1/2] arch: invoke oom-killer from page fault
Date: Thu, 6 Jun 2013 12:19:29 +0530	[thread overview]
Message-ID: <51B030F9.4080804@synopsys.com> (raw)
In-Reply-To: <20130606043620.GA9406@cmpxchg.org>

On 06/06/2013 10:06 AM, Johannes Weiner wrote:
> From: Johannes Weiner <hannes@cmpxchg.org>
> Subject: [patch] mm: invoke oom-killer from remaining unconverted page fault
>  handlers
> 
> A few remaining architectures directly kill the page faulting task in
> an out of memory situation.  This is usually not a good idea since
> that task might not even use a significant amount of memory and so may
> not be the optimal victim to resolve the situation.
> 
> Since '1c0fe6e mm: invoke oom-killer from page fault' (2.6.29) there
> is a hook that architecture page fault handlers are supposed to call
> to invoke the OOM killer and let it pick the right task to kill.
> Convert the remaining architectures over to this hook.
> 
> To have the previous behavior of simply taking out the faulting task
> the vm.oom_kill_allocating_task sysctl can be set to 1.
> 
> Signed-off-by: Johannes Weiner <hannes@cmpxchg.org>

Acked-by: Vineet Gupta <vgupta@synopsys.com>   # for arch/arc bits

  parent reply	other threads:[~2013-06-06  6:49 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-06  3:09 [patch 1/2] arch: invoke oom-killer from page fault Johannes Weiner
2013-06-06  3:09 ` Johannes Weiner
2013-06-06  3:09 ` [patch 2/2] memcg: do not sleep on OOM waitqueue with full charge context Johannes Weiner
2013-06-06  3:09   ` Johannes Weiner
2013-06-06  4:10   ` David Rientjes
2013-06-06  4:10     ` David Rientjes
2013-06-06  5:33     ` Johannes Weiner
2013-06-06  5:33       ` Johannes Weiner
2013-06-06 17:33       ` Johannes Weiner
2013-06-06 17:33         ` Johannes Weiner
2013-06-06 20:11         ` David Rientjes
2013-06-06 20:11           ` David Rientjes
2013-06-06 21:54           ` Johannes Weiner
2013-06-06 21:54             ` Johannes Weiner
2013-06-06 22:18             ` David Rientjes
2013-06-06 22:18               ` David Rientjes
2013-06-07  0:02               ` Johannes Weiner
2013-06-07  0:02                 ` Johannes Weiner
2013-06-11 21:57                 ` David Rientjes
2013-06-11 21:57                   ` David Rientjes
2013-06-12  8:28                   ` Michal Hocko
2013-06-12  8:28                     ` Michal Hocko
     [not found]                     ` <20130612082817.GA6706-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2013-06-12 20:12                       ` David Rientjes
2013-06-12 20:12                         ` David Rientjes
2013-06-12 20:12                         ` David Rientjes
2013-06-12 20:37                         ` Michal Hocko
2013-06-12 20:37                           ` Michal Hocko
2013-06-12 20:49                           ` David Rientjes
2013-06-12 20:49                             ` David Rientjes
2013-06-13 13:48                             ` Michal Hocko
2013-06-13 13:48                               ` Michal Hocko
2013-06-13 20:34                               ` David Rientjes
2013-06-13 20:34                                 ` David Rientjes
2013-06-14  9:29                                 ` Michal Hocko
2013-06-14  9:29                                   ` Michal Hocko
2013-06-06 15:23     ` Michal Hocko
2013-06-06 15:23       ` Michal Hocko
2013-06-06  3:57 ` [patch 1/2] arch: invoke oom-killer from page fault David Rientjes
2013-06-06  3:57   ` David Rientjes
2013-06-06  4:36   ` Johannes Weiner
2013-06-06  4:36     ` Johannes Weiner
2013-06-06  4:43     ` David Rientjes
2013-06-06  4:43       ` David Rientjes
2013-06-06  6:49     ` Vineet Gupta [this message]
2013-06-06  6:49       ` Vineet Gupta
2013-06-06  6:49       ` Vineet Gupta
     [not found]     ` <20130606043620.GA9406-druUgvl0LCNAfugRpC6u6w@public.gmane.org>
2013-06-06 14:59       ` Michal Hocko
2013-06-06 14:59         ` Michal Hocko
2013-06-06 14:59         ` Michal Hocko
2013-06-06  4:55 ` 刘胜蛟

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=51B030F9.4080804@synopsys.com \
    --to=vineet.gupta1@synopsys.com \
    --cc=akpm@linux-foundation.org \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.cz \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.