From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail172.messagelabs.com (mail172.messagelabs.com [216.82.254.3]) by kanga.kvack.org (Postfix) with SMTP id 647BF6B005D for ; Mon, 29 Jun 2009 10:58:42 -0400 (EDT) Received: by yxe38 with SMTP id 38so4103266yxe.12 for ; Mon, 29 Jun 2009 08:00:27 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <29432.1246285300@redhat.com> References: <26537.1246086769@redhat.com> <28c262360906280630n557bb182n5079e33d21ea4a83@mail.gmail.com> <28c262360906280636l93130ffk14086314e2a6dcb7@mail.gmail.com> <20090628142239.GA20986@localhost> <2f11576a0906280801w417d1b9fpe10585b7a641d41b@mail.gmail.com> <20090628151026.GB25076@localhost> <20090629091741.ab815ae7.minchan.kim@barrios-desktop> <17678.1246270219@redhat.com> <20090629125549.GA22932@localhost> <29432.1246285300@redhat.com> Date: Tue, 30 Jun 2009 00:00:26 +0900 Message-ID: <28c262360906290800v37f91d7av3642b1ad8b5f0477@mail.gmail.com> Subject: Re: Found the commit that causes the OOMs From: Minchan Kim Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Sender: owner-linux-mm@kvack.org To: David Howells , Mel Gorman Cc: Wu Fengguang , KOSAKI Motohiro , Johannes Weiner , "riel@redhat.com" , Andrew Morton , LKML , Christoph Lameter , "peterz@infradead.org" , "tytso@mit.edu" , "linux-mm@kvack.org" , "elladan@eskimo.com" , "npiggin@suse.de" , "Barnes, Jesse" List-ID: On Mon, Jun 29, 2009 at 11:21 PM, David Howells wrote: > Wu Fengguang wrote: > >> Sorry! This one compiles OK: > > Sadly that doesn't seem to work either: > > msgctl11 invoked oom-killer: gfp_mask=3D0x200da, order=3D0, oom_adj=3D0 > msgctl11 cpuset=3D/ mems_allowed=3D0 > Pid: 30858, comm: msgctl11 Not tainted 2.6.31-rc1-cachefs #146 > Call Trace: > =C2=A0[] ? oom_kill_process.clone.0+0xa9/0x245 > =C2=A0[] ? __out_of_memory+0x12b/0x142 > =C2=A0[] ? out_of_memory+0x6a/0x94 > =C2=A0[] ? __alloc_pages_nodemask+0x42e/0x51d > =C2=A0[] ? do_wp_page+0x2c6/0x5f5 > =C2=A0[] ? handle_mm_fault+0x5dd/0x62f > =C2=A0[] ? do_page_fault+0x1f8/0x20d > =C2=A0[] ? page_fault+0x1f/0x30 > Mem-Info: > DMA per-cpu: > CPU =C2=A0 =C2=A00: hi: =C2=A0 =C2=A00, btch: =C2=A0 1 usd: =C2=A0 0 > CPU =C2=A0 =C2=A01: hi: =C2=A0 =C2=A00, btch: =C2=A0 1 usd: =C2=A0 0 > DMA32 per-cpu: > CPU =C2=A0 =C2=A00: hi: =C2=A0186, btch: =C2=A031 usd: =C2=A038 > CPU =C2=A0 =C2=A01: hi: =C2=A0186, btch: =C2=A031 usd: 106 > Active_anon:75040 active_file:0 inactive_anon:2031 > =C2=A0inactive_file:0 unevictable:0 dirty:0 writeback:0 unstable:0 > =C2=A0free:1951 slab:41499 mapped:301 pagetables:60674 bounce:0 > DMA free:3932kB min:60kB low:72kB high:88kB active_anon:2868kB inactive_a= non:384kB active_file:0kB inactive_file:0kB unevictable:0kB present:15364kB= pages_scanned:0 all_unreclaimable? no > lowmem_reserve[]: 0 968 968 968 > DMA32 free:3872kB min:3948kB low:4932kB high:5920kB active_anon:297292kB = inactive_anon:7740kB active_file:0kB inactive_file:0kB unevictable:0kB pres= ent:992032kB pages_scanned:0 all_unreclaimable? no > lowmem_reserve[]: 0 0 0 0 > DMA: 7*4kB 0*8kB 0*16kB 0*32kB 1*64kB 0*128kB 1*256kB 1*512kB 1*1024kB 1*= 2048kB 0*4096kB =3D 3932kB > DMA32: 500*4kB 2*8kB 0*16kB 0*32kB 1*64kB 0*128kB 1*256kB 1*512kB 1*1024k= B 0*2048kB 0*4096kB =3D 3872kB > 1928 total pagecache pages > 0 pages in swap cache > Swap cache stats: add 0, delete 0, find 0/0 > Free swap =C2=A0=3D 0kB > Total swap =3D 0kB > 255744 pages RAM > 5589 pages reserved > 238251 pages shared > 216210 pages non-shared > Out of memory: kill process 25221 (msgctl11) score 130560 or a child > Killed process 26379 (msgctl11) Totally, I can't understand this situation. Now, this page allocation is order zero and It is just likely GFP_HIGHUSER. So it's unlikely interrupt context. Buddy already has enough fallback DMA32, I think. Why kernel can't allocate page for order 0 ? Is it allocator bug ? --=20 Kinds regards, Minchan Kim -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org