Re: [PATCH] mm: clarify COMPACTION Kconfig text

2016-08-29 Thread Michal Hocko
On Mon 29-08-16 10:10:45, Johannes Weiner wrote: > On Tue, Aug 23, 2016 at 10:09:17AM +0200, Michal Hocko wrote: > > From: Michal Hocko > > > > The current wording of the COMPACTION Kconfig help text doesn't > > emphasise that disabling COMPACTION might cripple the page allocator > > which relies

Re: [PATCH] mm: clarify COMPACTION Kconfig text

2016-08-29 Thread Johannes Weiner
On Tue, Aug 23, 2016 at 10:09:17AM +0200, Michal Hocko wrote: > From: Michal Hocko > > The current wording of the COMPACTION Kconfig help text doesn't > emphasise that disabling COMPACTION might cripple the page allocator > which relies on the compaction quite heavily for high order requests and

Re: [PATCH] mm: clarify COMPACTION Kconfig text

2016-08-25 Thread Michal Hocko
On Thu 25-08-16 15:34:54, David Rientjes wrote: > On Thu, 25 Aug 2016, Michal Hocko wrote: > > > > I don't believe it has been an issue in the past for any archs that > > > don't use thp. > > > > Well, fragmentation is a real problem and order-0 reclaim will be never > > anywhere close to reliabl

Re: [PATCH] mm: clarify COMPACTION Kconfig text

2016-08-25 Thread David Rientjes
On Thu, 25 Aug 2016, Michal Hocko wrote: > > I don't believe it has been an issue in the past for any archs that > > don't use thp. > > Well, fragmentation is a real problem and order-0 reclaim will be never > anywhere close to reliably provide higher order pages. Well, reclaiming > a lot of memo

Re: [PATCH] mm: clarify COMPACTION Kconfig text

2016-08-25 Thread Michal Hocko
On Wed 24-08-16 17:54:52, David Rientjes wrote: > On Tue, 23 Aug 2016, Michal Hocko wrote: > > > From: Michal Hocko > > > > The current wording of the COMPACTION Kconfig help text doesn't > > emphasise that disabling COMPACTION might cripple the page allocator > > which relies on the compaction

Re: [PATCH] mm: clarify COMPACTION Kconfig text

2016-08-24 Thread David Rientjes
On Tue, 23 Aug 2016, Michal Hocko wrote: > From: Michal Hocko > > The current wording of the COMPACTION Kconfig help text doesn't > emphasise that disabling COMPACTION might cripple the page allocator > which relies on the compaction quite heavily for high order requests and > an unexpected OOM

Re: [PATCH] mm: clarify COMPACTION Kconfig text

2016-08-23 Thread Michal Hocko
that at > would be Thanks for the review. Updated patch follows: --- >From 177212367432e9fa5e090fafdfe3774d5793e46b Mon Sep 17 00:00:00 2001 From: Michal Hocko Date: Tue, 23 Aug 2016 10:03:37 +0200 Subject: [PATCH] mm: clarify COMPACTION Kconfig text The curren

Re: [PATCH] mm: clarify COMPACTION Kconfig text

2016-08-23 Thread Markus Trippelsdorf
On 2016.08.23 at 10:09 +0200, Michal Hocko wrote: > From: Michal Hocko > > The current wording of the COMPACTION Kconfig help text doesn't > emphasise that disabling COMPACTION might cripple the page allocator > which relies on the compaction quite heavily for high order requests and > an unexpec

[PATCH] mm: clarify COMPACTION Kconfig text

2016-08-23 Thread Michal Hocko
From: Michal Hocko The current wording of the COMPACTION Kconfig help text doesn't emphasise that disabling COMPACTION might cripple the page allocator which relies on the compaction quite heavily for high order requests and an unexpected OOM can happen with the lack of compaction. Make sure we a