Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: blaterblater@hotmail.com (Frank)
To: linux-arm-kernel@lists.infradead.org
Subject: memory allocation errors on Marvell Kirkwood
Date: Sun, 28 Nov 2010 13:43:46 +0100	[thread overview]
Message-ID: <BLU0-SMTP32593CEE5C8F556A931E3BCF230@phx.gbl> (raw)
In-Reply-To: <20101128120857.GB23772@n2100.arm.linux.org.uk>

> -----Original Message-----
> From: Russell King - ARM Linux [mailto:linux at arm.linux.org.uk]
> Sent: Sunday, November 28, 2010 13:09
> To: Frank
> Cc: linux-arm-kernel at lists.infradead.org
> Subject: Re: memory allocation errors on Marvell Kirkwood
> 
> On Sun, Nov 28, 2010 at 12:44:56PM +0100, Frank wrote:
> > [323570.011580] swapper: page allocation failure. order:3,
> mode:0x4020
> 
> Order 3.  That's wanting 4K << 3, or 32K.
> 
> > [323570.289988] Normal: 1057*4kB 3870*8kB 99*16kB 0*32kB 0*64kB
> 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 36772kB
> 
> And from this line, we see that we have no pages larger than 16K
> available
> in the system, despite having 36MB of free memory.  IOW, your memory
> has
> become extremely fragmented.
> 
> We don't guaranttee that this doesn't happen - in fact, we explicitly
> tell
> people that memory fragmentation _does_ happen and we do _not_
> guarantee
> that allocations > order-0 will succeed.
> 
> From the backtrace, I guess you're using a network interface with a MTU
> larger than about 16K ?
<cut>

Physical network interface uses a MTU value of 1500. The ppp0 tunnel uses an MTU of 1400. Further note that I cannot reproduce this problem when transferring data with ftp directly over the physical network interface, nor when using cifs/smb over the ppp0 interface.

  reply	other threads:[~2010-11-28 12:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-28 11:44 memory allocation errors on Marvell Kirkwood Frank
2010-11-28 12:08 ` Russell King - ARM Linux
2010-11-28 12:43   ` Frank [this message]
2010-11-29 15:00   ` Frank

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=BLU0-SMTP32593CEE5C8F556A931E3BCF230@phx.gbl \
    --to=blaterblater@hotmail.com \
    --cc=linux-arm-kernel@lists.infradead.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