Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1413196

Re: [BUG] Page allocation failures with newest kernels

From Mel Gorman <mgorman@techsingularity.net>
Newsgroups linux.kernel
Subject Re: [BUG] Page allocation failures with newest kernels
Date 2016-06-03 14:40 +0200
Message-ID <rFWym-39X-29@gated-at.bofh.it> (permalink)
References (5 earlier) <rFtG1-1SZ-1@gated-at.bofh.it> <rFBkd-6AY-21@gated-at.bofh.it> <rFGad-1z0-5@gated-at.bofh.it> <rFU3w-1wB-23@gated-at.bofh.it> <rFVVE-2EE-27@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Fri, Jun 03, 2016 at 01:57:06PM +0200, Marcin Wojtas wrote:
> >> For the record: the newest kernel I was able to reproduce the dumps
> >> was v4.6: http://pastebin.com/ekDdACn5. I've just checked v4.7-rc1,
> >> which comprise a lot (mainly yours) changes in mm, and I'm wondering
> >> if there may be a spot fix or rather a series of improvements. I'm
> >> looking forward to your opinion and would be grateful for any advice.
> >>
> >
> > I don't believe we want to reintroduce the reserve to cope with CMA. One
> > option would be to widen the gap between low and min watermark by the
> > size of the CMA region. The effect would be to wake kswapd earlier which
> > matters considering the context of the failing allocation was
> > GFP_ATOMIC.
> 
> Of course my intention is not reintroducing anything that's gone
> forever, but just to find out way to overcome current issues. Do you
> mean increasing CMA size?

No. There is a gap between the low and min watermarks. At the low point,
kswapd is woken up and at the min point allocation requests either
either direct reclaim or fail if they are atomic. What I'm suggesting
is that you adjust the low watermark and add the size of the CMA area
to it so that kswapd is woken earlier. The watermarks are calculated in
__setup_per_zone_wmarks

-- 
Mel Gorman
SUSE Labs

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Re: [BUG] Page allocation failures with newest kernels Robin Murphy <robin.murphy@arm.com> - 2016-05-31 12:20 +0200
  Re: [BUG] Page allocation failures with newest kernels Marcin Wojtas <mw@semihalf.com> - 2016-05-31 12:40 +0200
    RE: [BUG] Page allocation failures with newest kernels Yehuda Yitschak <yehuday@marvell.com> - 2016-05-31 15:20 +0200
      Re: [BUG] Page allocation failures with newest kernels Will Deacon <will.deacon@arm.com> - 2016-05-31 15:20 +0200
        Re: [BUG] Page allocation failures with newest kernels Marcin Wojtas <mw@semihalf.com> - 2016-06-02 07:50 +0200
          Re: [BUG] Page allocation failures with newest kernels Mel Gorman <mgorman@techsingularity.net> - 2016-06-02 16:00 +0200
            Re: [BUG] Page allocation failures with newest kernels Marcin Wojtas <mw@semihalf.com> - 2016-06-02 21:10 +0200
              Re: [BUG] Page allocation failures with newest kernels Mel Gorman <mgorman@techsingularity.net> - 2016-06-03 12:00 +0200
                Re: [BUG] Page allocation failures with newest kernels Marcin Wojtas <mw@semihalf.com> - 2016-06-03 14:00 +0200
                Re: [BUG] Page allocation failures with newest kernels Mel Gorman <mgorman@techsingularity.net> - 2016-06-03 14:40 +0200
                Re: [BUG] Page allocation failures with newest kernels Marcin Wojtas <mw@semihalf.com> - 2016-06-07 19:40 +0200
                Re: [BUG] Page allocation failures with newest kernels Mel Gorman <mgorman@techsingularity.net> - 2016-06-08 12:20 +0200
                Re: [BUG] Page allocation failures with newest kernels Marcin Wojtas <mw@semihalf.com> - 2016-06-09 20:20 +0200
                Re: [BUG] Page allocation failures with newest kernels Marcin Wojtas <mw@semihalf.com> - 2016-06-10 18:10 +0200

csiph-web