From: Peter Zijlstra <peterz@infradead.org>
To: "Dan Noé" <dpn@isomerica.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Page alloc failures under network/disk IO load
Date: Thu, 04 Dec 2008 09:42:08 +0100 [thread overview]
Message-ID: <1228380128.5092.15.camel@twins> (raw)
In-Reply-To: <1228378983.5092.7.camel@twins>
On Thu, 2008-12-04 at 09:23 +0100, Peter Zijlstra wrote:
> On Wed, 2008-12-03 at 22:27 -0500, Dan Noé wrote:
> > This is on Linux 2.6.28-rc7, on a Core 2 Duo. The system has plenty of
> > memory:
> >
> > total used free shared buffers
> > cached
> > Mem: 1893 1822 70 0 0
>
> filled to the brim with data
>
> > 1573
> > -/+ buffers/cache: 249 1644
> > Swap: 1906 37 1868
> >
> > I am using rsync to transfer data onto this system. The filesystem is
> > XFS, and the target drive is a 1TB Western Digital on ata_piix. The
> > system files are on a RAID 1 (Linux md, also on ata_piix).
> >
> > Periodically I get page allocation failures, from __netdev_alloc_skb.
> > I suppose this causes the driver to drop packets and thus hurts
> > performance.
>
> There isn't much we can do about that, memory is filled and your network
> card tries to allocate memory in a mode that doesn't allow freeing some.
>
> Looking at the timestamps its not very frequent, so it doesn't hurt
> performance much if anything. If you're really bothered with this, you
> could quiet it by sticking in a __GFP_NOWARN in __netdev_alloc_skb() or
> something..
Another thing you can do is increase /proc/sys/vm/min_free_kbytes
next prev parent reply other threads:[~2008-12-04 8:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 3:27 Page alloc failures under network/disk IO load Dan Noé
2008-12-04 8:23 ` Peter Zijlstra
2008-12-04 8:42 ` Peter Zijlstra [this message]
2008-12-04 18:54 ` Dan Noé
2008-12-04 22:40 ` Francois Romieu
2008-12-04 23:09 ` Dan Noé
2008-12-05 4:08 ` Robert Hancock
2008-12-05 7:13 ` Peter Zijlstra
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=1228380128.5092.15.camel@twins \
--to=peterz@infradead.org \
--cc=dpn@isomerica.net \
--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