From: "Dan Noé" <dpn@isomerica.net>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: Peter Zijlstra <peterz@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: Page alloc failures under network/disk IO load
Date: Thu, 04 Dec 2008 18:09:19 -0500 [thread overview]
Message-ID: <4938631F.7010004@isomerica.net> (raw)
In-Reply-To: <20081204224021.GA323@electric-eye.fr.zoreil.com>
Francois Romieu wrote:
> Dan Noé <dpn@isomerica.net> :
> [...]
>> I'm a bit confused because on another system (2.6.26.3) I never see
>> messages like this despite having the same amount of physical RAM in
>> each. The 2.6.26.3 system is also under more active use, and has more
>> userspace memory usage. On that system:
>
> Does this system use the same network card ?
Nope, good point :) The system experiencing the allocation failures is
using an rtl8169 gigabit NIC (at 1gbps), the 2.6.26.3 system is on a
100M connection with a gigabit Broadcom BCM5721 / tg3.
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
04:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5721
Gigabit Ethernet PCI Express (rev 11)
I can see how this could account for different behavior, although
presumably both drivers are calling __netdev_alloc_skb.
Cheers,
Dan
--
/--------------- - - - - - -
| Dan Noé
| http://isomerica.net/~dpn/
next prev parent reply other threads:[~2008-12-04 23:09 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
2008-12-04 18:54 ` Dan Noé
2008-12-04 22:40 ` Francois Romieu
2008-12-04 23:09 ` Dan Noé [this message]
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=4938631F.7010004@isomerica.net \
--to=dpn@isomerica.net \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=romieu@fr.zoreil.com \
/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