Re: [patch 00/12] mm: page_alloc: improve OOM mechanism and policy

2015-04-14 Thread Michal Hocko
On Tue 14-04-15 06:36:25, Johannes Weiner wrote: > On Mon, Apr 13, 2015 at 02:46:14PM +0200, Michal Hocko wrote: [...] > > AFAIU, David wasn't asking for the OOM killer as much as he was > > interested in getting access to a small amount of reserves in order to > > make a progress. __GFP_HIGH is

Re: [patch 00/12] mm: page_alloc: improve OOM mechanism and policy

2015-04-14 Thread Johannes Weiner
On Mon, Apr 13, 2015 at 02:46:14PM +0200, Michal Hocko wrote: > [Sorry for a late reply] > > On Tue 07-04-15 10:18:22, Johannes Weiner wrote: > > On Wed, Apr 01, 2015 at 05:19:20PM +0200, Michal Hocko wrote: > > > On Mon 30-03-15 11:32:40, Dave Chinner wrote: > > > > On Fri, Mar 27, 2015 at

Re: [patch 00/12] mm: page_alloc: improve OOM mechanism and policy

2015-04-14 Thread Michal Hocko
On Tue 14-04-15 10:11:18, Dave Chinner wrote: > On Mon, Apr 13, 2015 at 02:46:14PM +0200, Michal Hocko wrote: > > [Sorry for a late reply] > > > > On Tue 07-04-15 10:18:22, Johannes Weiner wrote: > > > On Wed, Apr 01, 2015 at 05:19:20PM +0200, Michal Hocko wrote: > > > My question here would be:

Re: [patch 00/12] mm: page_alloc: improve OOM mechanism and policy

2015-04-14 Thread Michal Hocko
On Tue 14-04-15 10:11:18, Dave Chinner wrote: On Mon, Apr 13, 2015 at 02:46:14PM +0200, Michal Hocko wrote: [Sorry for a late reply] On Tue 07-04-15 10:18:22, Johannes Weiner wrote: On Wed, Apr 01, 2015 at 05:19:20PM +0200, Michal Hocko wrote: My question here would be: are there any

Re: [patch 00/12] mm: page_alloc: improve OOM mechanism and policy

2015-04-14 Thread Johannes Weiner
On Mon, Apr 13, 2015 at 02:46:14PM +0200, Michal Hocko wrote: [Sorry for a late reply] On Tue 07-04-15 10:18:22, Johannes Weiner wrote: On Wed, Apr 01, 2015 at 05:19:20PM +0200, Michal Hocko wrote: On Mon 30-03-15 11:32:40, Dave Chinner wrote: On Fri, Mar 27, 2015 at 11:05:09AM -0400,

Re: [patch 00/12] mm: page_alloc: improve OOM mechanism and policy

2015-04-14 Thread Michal Hocko
On Tue 14-04-15 06:36:25, Johannes Weiner wrote: On Mon, Apr 13, 2015 at 02:46:14PM +0200, Michal Hocko wrote: [...] AFAIU, David wasn't asking for the OOM killer as much as he was interested in getting access to a small amount of reserves in order to make a progress. __GFP_HIGH is there

Re: [patch 00/12] mm: page_alloc: improve OOM mechanism and policy

2015-04-13 Thread Dave Chinner
On Mon, Apr 13, 2015 at 02:46:14PM +0200, Michal Hocko wrote: > [Sorry for a late reply] > > On Tue 07-04-15 10:18:22, Johannes Weiner wrote: > > On Wed, Apr 01, 2015 at 05:19:20PM +0200, Michal Hocko wrote: > > My question here would be: are there any NOFS allocations that *don't* > > want this

Re: [patch 00/12] mm: page_alloc: improve OOM mechanism and policy

2015-04-13 Thread Michal Hocko
On Sat 11-04-15 16:29:26, Tetsuo Handa wrote: > Johannes Weiner wrote: > > The argument here was always that NOFS allocations are very limited in > > their reclaim powers and will trigger OOM prematurely. However, the > > way we limit dirty memory these days forces most cache to be clean at > >

Re: [patch 00/12] mm: page_alloc: improve OOM mechanism and policy

2015-04-13 Thread Michal Hocko
[Sorry for a late reply] On Tue 07-04-15 10:18:22, Johannes Weiner wrote: > On Wed, Apr 01, 2015 at 05:19:20PM +0200, Michal Hocko wrote: > > On Mon 30-03-15 11:32:40, Dave Chinner wrote: > > > On Fri, Mar 27, 2015 at 11:05:09AM -0400, Johannes Weiner wrote: > > [...] > > > > GFP_NOFS sites are

Re: [patch 00/12] mm: page_alloc: improve OOM mechanism and policy

2015-04-13 Thread Dave Chinner
On Mon, Apr 13, 2015 at 02:46:14PM +0200, Michal Hocko wrote: [Sorry for a late reply] On Tue 07-04-15 10:18:22, Johannes Weiner wrote: On Wed, Apr 01, 2015 at 05:19:20PM +0200, Michal Hocko wrote: My question here would be: are there any NOFS allocations that *don't* want this behavior?

Re: [patch 00/12] mm: page_alloc: improve OOM mechanism and policy

2015-04-13 Thread Michal Hocko
On Sat 11-04-15 16:29:26, Tetsuo Handa wrote: Johannes Weiner wrote: The argument here was always that NOFS allocations are very limited in their reclaim powers and will trigger OOM prematurely. However, the way we limit dirty memory these days forces most cache to be clean at all times,

Re: [patch 00/12] mm: page_alloc: improve OOM mechanism and policy

2015-04-13 Thread Michal Hocko
[Sorry for a late reply] On Tue 07-04-15 10:18:22, Johannes Weiner wrote: On Wed, Apr 01, 2015 at 05:19:20PM +0200, Michal Hocko wrote: On Mon 30-03-15 11:32:40, Dave Chinner wrote: On Fri, Mar 27, 2015 at 11:05:09AM -0400, Johannes Weiner wrote: [...] GFP_NOFS sites are currently one

Re: [patch 00/12] mm: page_alloc: improve OOM mechanism and policy

2015-04-11 Thread Tetsuo Handa
Johannes Weiner wrote: > The argument here was always that NOFS allocations are very limited in > their reclaim powers and will trigger OOM prematurely. However, the > way we limit dirty memory these days forces most cache to be clean at > all times, and direct reclaim in general hasn't been

Re: [patch 00/12] mm: page_alloc: improve OOM mechanism and policy

2015-04-11 Thread Tetsuo Handa
Johannes Weiner wrote: The argument here was always that NOFS allocations are very limited in their reclaim powers and will trigger OOM prematurely. However, the way we limit dirty memory these days forces most cache to be clean at all times, and direct reclaim in general hasn't been allowed

Re: [patch 00/12] mm: page_alloc: improve OOM mechanism and policy

2015-04-07 Thread Johannes Weiner
On Wed, Apr 01, 2015 at 05:19:20PM +0200, Michal Hocko wrote: > On Mon 30-03-15 11:32:40, Dave Chinner wrote: > > On Fri, Mar 27, 2015 at 11:05:09AM -0400, Johannes Weiner wrote: > [...] > > > GFP_NOFS sites are currently one of the sites that can deadlock inside > > > the allocator, even though

Re: [patch 00/12] mm: page_alloc: improve OOM mechanism and policy

2015-04-07 Thread Johannes Weiner
On Wed, Apr 01, 2015 at 05:19:20PM +0200, Michal Hocko wrote: On Mon 30-03-15 11:32:40, Dave Chinner wrote: On Fri, Mar 27, 2015 at 11:05:09AM -0400, Johannes Weiner wrote: [...] GFP_NOFS sites are currently one of the sites that can deadlock inside the allocator, even though many of

Re: [patch 00/12] mm: page_alloc: improve OOM mechanism and policy

2015-04-02 Thread Michal Hocko
On Thu 02-04-15 08:39:02, Dave Chinner wrote: > On Wed, Apr 01, 2015 at 05:19:20PM +0200, Michal Hocko wrote: > > On Mon 30-03-15 11:32:40, Dave Chinner wrote: > > > On Fri, Mar 27, 2015 at 11:05:09AM -0400, Johannes Weiner wrote: > > [...] > > > > GFP_NOFS sites are currently one of the sites

Re: [patch 00/12] mm: page_alloc: improve OOM mechanism and policy

2015-04-02 Thread Michal Hocko
On Thu 02-04-15 08:39:02, Dave Chinner wrote: On Wed, Apr 01, 2015 at 05:19:20PM +0200, Michal Hocko wrote: On Mon 30-03-15 11:32:40, Dave Chinner wrote: On Fri, Mar 27, 2015 at 11:05:09AM -0400, Johannes Weiner wrote: [...] GFP_NOFS sites are currently one of the sites that can

Re: [patch 00/12] mm: page_alloc: improve OOM mechanism and policy

2015-04-01 Thread Dave Chinner
On Wed, Apr 01, 2015 at 05:19:20PM +0200, Michal Hocko wrote: > On Mon 30-03-15 11:32:40, Dave Chinner wrote: > > On Fri, Mar 27, 2015 at 11:05:09AM -0400, Johannes Weiner wrote: > [...] > > > GFP_NOFS sites are currently one of the sites that can deadlock inside > > > the allocator, even though

Re: [patch 00/12] mm: page_alloc: improve OOM mechanism and policy

2015-04-01 Thread Michal Hocko
On Mon 30-03-15 11:32:40, Dave Chinner wrote: > On Fri, Mar 27, 2015 at 11:05:09AM -0400, Johannes Weiner wrote: [...] > > GFP_NOFS sites are currently one of the sites that can deadlock inside > > the allocator, even though many of them seem to have fallback code. > > My reasoning here is that if

Re: [patch 00/12] mm: page_alloc: improve OOM mechanism and policy

2015-04-01 Thread Michal Hocko
On Mon 30-03-15 11:32:40, Dave Chinner wrote: On Fri, Mar 27, 2015 at 11:05:09AM -0400, Johannes Weiner wrote: [...] GFP_NOFS sites are currently one of the sites that can deadlock inside the allocator, even though many of them seem to have fallback code. My reasoning here is that if you

Re: [patch 00/12] mm: page_alloc: improve OOM mechanism and policy

2015-04-01 Thread Dave Chinner
On Wed, Apr 01, 2015 at 05:19:20PM +0200, Michal Hocko wrote: On Mon 30-03-15 11:32:40, Dave Chinner wrote: On Fri, Mar 27, 2015 at 11:05:09AM -0400, Johannes Weiner wrote: [...] GFP_NOFS sites are currently one of the sites that can deadlock inside the allocator, even though many of

Re: [patch 00/12] mm: page_alloc: improve OOM mechanism and policy

2015-03-30 Thread Johannes Weiner
On Mon, Mar 30, 2015 at 11:32:40AM +1100, Dave Chinner wrote: > On Fri, Mar 27, 2015 at 11:05:09AM -0400, Johannes Weiner wrote: > > GFP_NOFS sites are currently one of the sites that can deadlock inside > > the allocator, even though many of them seem to have fallback code. > > My reasoning here

Re: [patch 00/12] mm: page_alloc: improve OOM mechanism and policy

2015-03-30 Thread Johannes Weiner
On Mon, Mar 30, 2015 at 11:32:40AM +1100, Dave Chinner wrote: On Fri, Mar 27, 2015 at 11:05:09AM -0400, Johannes Weiner wrote: GFP_NOFS sites are currently one of the sites that can deadlock inside the allocator, even though many of them seem to have fallback code. My reasoning here is that

Re: [patch 00/12] mm: page_alloc: improve OOM mechanism and policy

2015-03-29 Thread Dave Chinner
On Fri, Mar 27, 2015 at 11:05:09AM -0400, Johannes Weiner wrote: > On Fri, Mar 27, 2015 at 06:58:22AM +1100, Dave Chinner wrote: > > On Wed, Mar 25, 2015 at 02:17:04AM -0400, Johannes Weiner wrote: > > > Hi everybody, > > > > > > in the recent past we've had several reports and discussions on how

Re: [patch 00/12] mm: page_alloc: improve OOM mechanism and policy

2015-03-29 Thread Dave Chinner
On Fri, Mar 27, 2015 at 11:05:09AM -0400, Johannes Weiner wrote: On Fri, Mar 27, 2015 at 06:58:22AM +1100, Dave Chinner wrote: On Wed, Mar 25, 2015 at 02:17:04AM -0400, Johannes Weiner wrote: Hi everybody, in the recent past we've had several reports and discussions on how to deal

Re: [patch 00/12] mm: page_alloc: improve OOM mechanism and policy

2015-03-27 Thread Johannes Weiner
On Fri, Mar 27, 2015 at 06:58:22AM +1100, Dave Chinner wrote: > On Wed, Mar 25, 2015 at 02:17:04AM -0400, Johannes Weiner wrote: > > Hi everybody, > > > > in the recent past we've had several reports and discussions on how to > > deal with allocations hanging in the allocator upon OOM. > > > >

Re: [patch 00/12] mm: page_alloc: improve OOM mechanism and policy

2015-03-27 Thread Johannes Weiner
On Fri, Mar 27, 2015 at 06:58:22AM +1100, Dave Chinner wrote: On Wed, Mar 25, 2015 at 02:17:04AM -0400, Johannes Weiner wrote: Hi everybody, in the recent past we've had several reports and discussions on how to deal with allocations hanging in the allocator upon OOM. The idea of

Re: [patch 00/12] mm: page_alloc: improve OOM mechanism and policy

2015-03-26 Thread Dave Chinner
On Wed, Mar 25, 2015 at 02:17:04AM -0400, Johannes Weiner wrote: > Hi everybody, > > in the recent past we've had several reports and discussions on how to > deal with allocations hanging in the allocator upon OOM. > > The idea of this series is mainly to make the mechanism of detecting > OOM

Re: [patch 00/12] mm: page_alloc: improve OOM mechanism and policy

2015-03-26 Thread Dave Chinner
On Wed, Mar 25, 2015 at 02:17:04AM -0400, Johannes Weiner wrote: Hi everybody, in the recent past we've had several reports and discussions on how to deal with allocations hanging in the allocator upon OOM. The idea of this series is mainly to make the mechanism of detecting OOM

[patch 00/12] mm: page_alloc: improve OOM mechanism and policy

2015-03-25 Thread Johannes Weiner
Hi everybody, in the recent past we've had several reports and discussions on how to deal with allocations hanging in the allocator upon OOM. The idea of this series is mainly to make the mechanism of detecting OOM situations reliable enough that we can be confident about failing allocations,

[patch 00/12] mm: page_alloc: improve OOM mechanism and policy

2015-03-25 Thread Johannes Weiner
Hi everybody, in the recent past we've had several reports and discussions on how to deal with allocations hanging in the allocator upon OOM. The idea of this series is mainly to make the mechanism of detecting OOM situations reliable enough that we can be confident about failing allocations,