On 05/16/2016 09:17 AM, Vlastimil Babka wrote:
>Wouldn't it be better to pull the prio check into compaction_deferred
>directly? There are more callers and I am not really sure all of them
>would behave consistently.
I'll check, thanks.
Hm so the other callers of compaction_deferred() are in t
On Mon 16-05-16 09:17:11, Vlastimil Babka wrote:
> On 05/13/2016 03:38 PM, Michal Hocko wrote:
> > On Tue 10-05-16 09:36:01, Vlastimil Babka wrote:
[...]
> > > such as hugetlbfs allocations, and reduce some corner-case OOM's for
> > > non-costly
> > > allocations.
> >
> > My testing has shown tha
On 05/13/2016 03:38 PM, Michal Hocko wrote:
On Tue 10-05-16 09:36:01, Vlastimil Babka wrote:
During reclaim/compaction loop, it's desirable to get a final answer from
unsuccessful compaction so we can either fail the allocation or invoke the OOM
killer. However, heuristics such as deferred compa
On Tue 10-05-16 09:36:01, Vlastimil Babka wrote:
> During reclaim/compaction loop, it's desirable to get a final answer from
> unsuccessful compaction so we can either fail the allocation or invoke the OOM
> killer. However, heuristics such as deferred compaction or pageblock skip bits
> can cause
During reclaim/compaction loop, it's desirable to get a final answer from
unsuccessful compaction so we can either fail the allocation or invoke the OOM
killer. However, heuristics such as deferred compaction or pageblock skip bits
can cause compaction to skip parts or whole zones and lead to prema
5 matches
Mail list logo
