Re: (2) [PATCH v2] page_alloc: consider highatomic reserve in wmartermark fast

On 06/17/20 at 12:46am, Jaewon Kim wrote: ... > > > >>> i.e) > > > >>> In following situation, watermark check fails (9MB - 8MB < 4MB) > > > >>> though there are > > > >>> enough free (9MB - 4MB > 4MB). If this is really matter, we need to > > > >>> count highatomic > > > >>> free accurately. > >

Re: (2) [PATCH v2] page_alloc: consider highatomic reserve in wmartermark fast

., 2020년 6월 16일 (화) 오후 11:17, Baoquan He 님이 작성: > > On 06/16/20 at 04:30pm, 김재원 wrote: > > >>> > > <4>[ 6207.637627] [3: Binder:9343_3:22875] Normal free:10908kB > > >>> > > min:6192kB low:44388kB high:47060kB active_anon:409160kB > > >>> > > inactive_anon:325924kB active_file:235820kB inactiv

Re: (2) [PATCH v2] page_alloc: consider highatomic reserve in wmartermark fast

On 06/16/20 at 04:30pm, 김재원 wrote: > >>> > > <4>[ 6207.637627] [3: Binder:9343_3:22875] Normal free:10908kB > >>> > > min:6192kB low:44388kB high:47060kB active_anon:409160kB > >>> > > inactive_anon:325924kB active_file:235820kB inactive_file:276628kB > >>> > > unevictable:2444kB writepending:

RE:(2) [PATCH v2] page_alloc: consider highatomic reserve in wmartermark fast

>On 6/14/20 1:17 AM, Baoquan He wrote: >> On 06/13/20 at 10:08pm, Jaewon Kim wrote: >> ... >>> > > This is an example of ALLOC_HARDER allocation failure. >>> > > >>> > > <4>[ 6207.637280] [3: Binder:9343_3:22875] Binder:9343_3: page >>> > > allocation failure: order:0, mode:0x480020(GFP_ATOMIC),