From: Anton Blanchard <anton@samba.org>
To: Joonas Kortesalmi <joneskoo@derbian.org>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: swapper: page allocation failure. order:3, mode:0x20
Date: Thu, 1 Jan 2004 21:15:41 +1100 [thread overview]
Message-ID: <20040101101541.GJ28023@krispykreme> (raw)
In-Reply-To: <20040101093553.GA24788@derbian.org>
Hi,
> After running 2.6.0 on a server for a few days, I met an interesting and
> annoying problem. I was playing with NFS over gigabit ethernet (e1000) and
> it was a bit slow. I tried to find out why by running top and I saw syslog-ng
> eating almost 10% of the 1,3GHz Duron. Looked at the log and there was a huge
> flood of these messages:
>
> swapper: page allocation failure. order:3, mode:0x20
> irssi: page allocation failure. order:3, mode:0x20
> swapper: page allocation failure. order:3, mode:0x20
> vim: page allocation failure. order:3, mode:0x20
> swapper: page allocation failure. order:3, mode:0x20
Its sounds like you are using either a large MTU (9k?) or TSO. TSO
causes the networking stack to think it has a massive MTU and the e1000
card busts it up into proper MTU sized packets. The problem is that
it places much more stress on the allocator by asking for these large
chunks of memory in interrupt context.
Now e1000 uses TSO (and can regularly ask for 32kB+ kmallocs in
interrupt context) perhaps we should look moving the rx buffer refill code
into a context that can sleep. Then again its not like we can tolerate
much latency in this code path, your rx ring will run out quite quickly :)
BTW We have found increasing /proc/sys/vm/min_free_kbytes can help the
situation a bit. Bumping the slab limits for the larger kmallocs (via
echo X Y Z > /proc/slab) might be useful too.
We should probably rate limit that printk. Andrew: I was thinking of
stealing net_ratelimit and calling it core_ratelimit or whatever. Then
wrap these non critical things with it. Overkill?
Anton
next prev parent reply other threads:[~2004-01-01 10:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-01 9:35 swapper: page allocation failure. order:3, mode:0x20 Joonas Kortesalmi
2004-01-01 10:15 ` Anton Blanchard [this message]
2004-01-01 10:25 ` Andrew Morton
2004-01-01 13:01 ` Anton Blanchard
2004-01-01 20:45 ` Andrew Morton
2004-01-01 22:43 ` Anton Blanchard
2004-01-01 22:08 ` Christophe Saout
2004-01-01 22:45 ` Anton Blanchard
2004-01-01 23:13 ` Christophe Saout
2004-01-01 10:27 ` Anton Blanchard
2004-01-01 10:42 ` Arjan van de Ven
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=20040101101541.GJ28023@krispykreme \
--to=anton@samba.org \
--cc=akpm@osdl.org \
--cc=joneskoo@derbian.org \
--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