From: Aubrey <aubreylee@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: page allocation failure when cached memory is close to the total memory.
Date: Wed, 1 Mar 2006 17:54:43 +0800 [thread overview]
Message-ID: <6d6a94c50603010154hbbcdb68n8cd7e05f7f30aba5@mail.gmail.com> (raw)
Hi all,
I'm working on the blackfin uclinux. And the kernel version is 2.6.12.
I have an application to malloc 0Mb memory. When cached memory is
small, the allocation will be successful.
But when the cached memory is close to the total memory. The
applicaton memory allocation will fail. See below. I think the cached
memory should be released when there is no enough free memory to
allocate. So far no idea what's wrong. Did anyone ever run into the
problem? Many thanks to your any suggestions and comments.
Regards,
-Aubrey
=========================================================
root:/mnt> cat /proc/meminfo
MemTotal: 54600 kB
MemFree: 6228 kB
Buffers: 2340 kB
Cached: 38464 kB
SwapCached: 0 kB
Active: 11432 kB
Inactive: 29348 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 54600 kB
LowFree: 6228 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 6904 kB
Writeback: 0 kB
Mapped: 0 kB
Slab: 7292 kB
CommitLimit: 27300 kB
Committed_AS: 0 kB
PageTables: 0 kB
VmallocTotal: 0 kB
VmallocUsed: 0 kB
VmallocChunk: 0 kB
root:/mnt> ../ma
ma: page allocation failure. order:12, mode:0xd0
Stack from 0137bddc:<0>
<0> 00000000<0> 00024cb0<0> 00072b88<0>
036b8220<0> 0000000c<0> 000000d0<0>
00000000<0> 00000000<0>
<0> 00000010<0> 00000000<0> 001be5ec<0>
000270c6<0> 001bf760<0> 001bf640<0>
001be5e0<0> 00000001<0>
<0> 00000000<0> 000000d0<0> 00000000<0>
0000001f<0> 00000000<0> 00102758<0>
0000000e<0> 00000001<0>
<0> 000000d0<0> 0304ca60<0> 00026e8e<0>
00000000<0> 0270bb60<0> 00000021<0>
0000ffff<0> 00000073<0>
<0> 00000000<0> 00000004<0> 00000000<0>
0002aee0<0> 00000000<0> 0002b19c<0>
00000003<0> 001035bc<0>
<0> 03576c00<0> 0000000e<0> 00000021<0>
0368f00c<0> 009f7d54<0> 0002d460<0>
00000004<0> 00a00000<0>
Call Trace:<0>
<0> [<00003706>]<0>
[<0002d55e>]<0> [<00006f3e>]<0>
[<000036a4>]<0>
<0> [<00008000>]<0>
[<00007cd4>]<0> [<00001004>]<0>
Allocation of length 10485760 from process 144 failed
DMA per-cpu: empty
Normal per-cpu:
cpu 0 hot: low 14, high 42, batch 7
cpu 0 cold: low 0, high 14, batch 7
HighMem per-cpu: empty
Free pages: 7536kB (0kB HighMem)
Active:2794 inactive:7321 dirty:1725 writeback:1 unstable:0 free:1884
slab:1564 mapped:0 pagetables:0
DMA free:0kB min:0kB low:0kB high:0kB active:0kB inactive:0kB
present:0kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 55 55
Normal free:7536kB min:948kB low:1184kB high:1420kB active:11176kB
inactive:29284kB present:56320kB pages_scanned:0 all_unreclaimable?
no
lowmem_reserve[]: 0 0 0
HighMem free:0kB min:128kB low:160kB high:192kB active:0kB
inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0
DMA: empty
Normal: 58*4kB 7*8kB 3*16kB 1*32kB 0*64kB 0*128kB 0*256kB 6*512kB
4*1024kB 0*2048kB 0*4096kB 0*8192kB 0*16384kB 0*32768kB = 7536kB
HighMem: empty
Alloc failed
================================================================
next reply other threads:[~2006-03-01 9:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 9:54 Aubrey [this message]
2006-03-01 10:36 ` Andrew Morton
2006-03-02 3:37 ` Aubrey
2006-03-02 4:01 ` Andrew Morton
2006-03-02 4:03 ` Nick Piggin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6d6a94c50603010154hbbcdb68n8cd7e05f7f30aba5@mail.gmail.com \
--to=aubreylee@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®