From: Attila Kinali <attila@kinali.ch>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: linux-mm@kvack.org
Subject: Re: page allocation failure - still unfixed in 2.6.32.1
Date: Sun, 20 Dec 2009 13:00:43 +0100 [thread overview]
Message-ID: <20091220130043.dac8aa88.attila@kinali.ch> (raw)
In-Reply-To: <alpine.DEB.1.10.0912201250310.23464@uplift.swm.pp.se>
On Sun, 20 Dec 2009 12:52:23 +0100 (CET)
Mikael Abrahamsson <swmike@swm.pp.se> wrote:
> > The page allocation failure that was introduced in 2.6.31 and
> > which has been discussed here a few times, is still present in
> > 2.6.32.1. I can still (more or less) reproduce it on my home-fileserver:
> >
> > Dec 20 11:43:14 koyomi kernel: swapper: page allocation failure. order:3, mode:0x20
> > Dec 20 11:43:14 koyomi kernel: Pid: 0, comm: swapper Not tainted 2.6.32.1 #1
> > Dec 20 11:43:14 koyomi kernel: Call Trace:
>
> Are you sure these are new? I've been seeing them sporadically for years,
> this latest one is on 2.6.28. They seem to happen whenever there are lots
> of TCP sessions going, and I have raised the default TCP parameters for
> long latency performance.
Yes. I didn't see any such problems until i updated to 2.6.30.x.
And as the machine is mostly used for NFSv3, 99% of the traffic
is UDP and not TCP.
A quick count shows currently 17 TCP connections running.
So i dont think i'd hit any limit there.
Attila Kinali
--
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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2009-12-20 12:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-20 11:47 Attila Kinali
2009-12-20 11:52 ` Mikael Abrahamsson
2009-12-20 12:00 ` Attila Kinali [this message]
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=20091220130043.dac8aa88.attila@kinali.ch \
--to=attila@kinali.ch \
--cc=linux-mm@kvack.org \
--cc=swmike@swm.pp.se \
/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