Re: [PATCH] mm,oom: Re-enable OOM killer using timers.

2016-01-26 Thread David Rientjes
On Fri, 22 Jan 2016, Tetsuo Handa wrote: > > > (1) Design and use a system with appropriate memory capacity in mind. > > > > > > (2) When (1) failed, the OOM killer is invoked. The OOM killer selects > > > an OOM victim and allow that victim access to memory reserves by > > >

Re: [PATCH] mm,oom: Re-enable OOM killer using timers.

2016-01-26 Thread David Rientjes
On Fri, 22 Jan 2016, Tetsuo Handa wrote: > > > (1) Design and use a system with appropriate memory capacity in mind. > > > > > > (2) When (1) failed, the OOM killer is invoked. The OOM killer selects > > > an OOM victim and allow that victim access to memory reserves by > > >

Re: [PATCH] mm,oom: Re-enable OOM killer using timers.

2016-01-22 Thread Johannes Weiner
On Fri, Jan 22, 2016 at 10:59:10PM +0900, Tetsuo Handa wrote: > David Rientjes wrote: > > On Thu, 21 Jan 2016, Tetsuo Handa wrote: > > > > > I consider phases for managing system-wide OOM events as follows. > > > > > > (1) Design and use a system with appropriate memory capacity in mind. > > >

Re: [PATCH] mm,oom: Re-enable OOM killer using timers.

2016-01-22 Thread Tetsuo Handa
David Rientjes wrote: > On Thu, 21 Jan 2016, Tetsuo Handa wrote: > > > I consider phases for managing system-wide OOM events as follows. > > > > (1) Design and use a system with appropriate memory capacity in mind. > > > > (2) When (1) failed, the OOM killer is invoked. The OOM killer

Re: [PATCH] mm,oom: Re-enable OOM killer using timers.

2016-01-22 Thread Tetsuo Handa
David Rientjes wrote: > On Thu, 21 Jan 2016, Tetsuo Handa wrote: > > > I consider phases for managing system-wide OOM events as follows. > > > > (1) Design and use a system with appropriate memory capacity in mind. > > > > (2) When (1) failed, the OOM killer is invoked. The OOM killer

Re: [PATCH] mm,oom: Re-enable OOM killer using timers.

2016-01-22 Thread Johannes Weiner
On Fri, Jan 22, 2016 at 10:59:10PM +0900, Tetsuo Handa wrote: > David Rientjes wrote: > > On Thu, 21 Jan 2016, Tetsuo Handa wrote: > > > > > I consider phases for managing system-wide OOM events as follows. > > > > > > (1) Design and use a system with appropriate memory capacity in mind. > > >

Re: [PATCH] mm,oom: Re-enable OOM killer using timers.

2016-01-21 Thread David Rientjes
On Thu, 21 Jan 2016, Tetsuo Handa wrote: > I consider phases for managing system-wide OOM events as follows. > > (1) Design and use a system with appropriate memory capacity in mind. > > (2) When (1) failed, the OOM killer is invoked. The OOM killer selects > an OOM victim and allow

Re: [PATCH] mm,oom: Re-enable OOM killer using timers.

2016-01-21 Thread Tetsuo Handa
David Rientjes wrote: > On Wed, 20 Jan 2016, Tetsuo Handa wrote: > > > > > My goal is to ask the OOM killer not to toss the OOM killer's duty away. > > > > What is important for me is that the OOM killer takes next action when > > > > current action did not solve the OOM situation. > > > > > > >

Re: [PATCH] mm,oom: Re-enable OOM killer using timers.

2016-01-21 Thread Tetsuo Handa
David Rientjes wrote: > On Wed, 20 Jan 2016, Tetsuo Handa wrote: > > > > > My goal is to ask the OOM killer not to toss the OOM killer's duty away. > > > > What is important for me is that the OOM killer takes next action when > > > > current action did not solve the OOM situation. > > > > > > >

Re: [PATCH] mm,oom: Re-enable OOM killer using timers.

2016-01-21 Thread David Rientjes
On Thu, 21 Jan 2016, Tetsuo Handa wrote: > I consider phases for managing system-wide OOM events as follows. > > (1) Design and use a system with appropriate memory capacity in mind. > > (2) When (1) failed, the OOM killer is invoked. The OOM killer selects > an OOM victim and allow

Re: [PATCH] mm,oom: Re-enable OOM killer using timers.

2016-01-20 Thread David Rientjes
On Wed, 20 Jan 2016, Tetsuo Handa wrote: > > > My goal is to ask the OOM killer not to toss the OOM killer's duty away. > > > What is important for me is that the OOM killer takes next action when > > > current action did not solve the OOM situation. > > > > > > > What is the "next action" when

Re: [PATCH] mm,oom: Re-enable OOM killer using timers.

2016-01-20 Thread David Rientjes
On Wed, 20 Jan 2016, Tetsuo Handa wrote: > > > My goal is to ask the OOM killer not to toss the OOM killer's duty away. > > > What is important for me is that the OOM killer takes next action when > > > current action did not solve the OOM situation. > > > > > > > What is the "next action" when

[PATCH] mm,oom: Re-enable OOM killer using timers.

2016-01-07 Thread Tetsuo Handa
>From 2f73abcec47535062d41c04bd7d9068cd71214b0 Mon Sep 17 00:00:00 2001 From: Tetsuo Handa Date: Thu, 7 Jan 2016 11:34:41 +0900 Subject: [PATCH] mm,oom: Re-enable OOM killer using timers. This patch introduces two timers ( holdoff timer and victim wait timer) and sysctl variables for chang

[PATCH] mm,oom: Re-enable OOM killer using timers.

2016-01-07 Thread Tetsuo Handa
>From 2f73abcec47535062d41c04bd7d9068cd71214b0 Mon Sep 17 00:00:00 2001 From: Tetsuo Handa <penguin-ker...@i-love.sakura.ne.jp> Date: Thu, 7 Jan 2016 11:34:41 +0900 Subject: [PATCH] mm,oom: Re-enable OOM killer using timers. This patch introduces two timers ( holdoff timer and victim w