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
> > >
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
> > >
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.
> > >
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
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
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.
> > >
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
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.
> > > >
> > >
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.
> > > >
> > >
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
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
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
>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
>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
14 matches
Mail list logo