public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Rankin <rankincj@yahoo.com>
To: David Miller <davem@davemloft.net>,
	Eric Dumazet <eric.dumazet@gmail.com>
Cc: "e1000-devel@lists.sourceforge.net"
	<e1000-devel@lists.sourceforge.net>,
	Tushar NDave <tushar.n.dave@intel.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Subject: RE: [E1000-devel] [e100] Page allocation failure warning(?) in 2.6.36.3
Date: Wed, 12 Jan 2011 09:42:13 -0800 (PST)	[thread overview]
Message-ID: <247288.34804.qm@web121705.mail.ne1.yahoo.com> (raw)
In-Reply-To: <1294853710.3981.108.camel@edumazet-laptop>

--- On Wed, 12/1/11, Eric Dumazet <eric.dumazet@gmail.com> wrote:
> Apparently e100 driver uses GFP_ATOMIC allocations in setup
> phase, and your machine doesnt have enough memory.

Thanks. You'd think 64 MB of RAM would be enough... ;-).

Cheers,
Chris


      

  reply	other threads:[~2011-01-12 17:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-08 12:53 [e100] Page allocation failure warning(?) in 2.6.36.3 Chris Rankin
2011-01-10 23:11 ` [E1000-devel] " Dave, Tushar N
2011-01-10 23:41   ` Chris Rankin
2011-01-11  0:37     ` Dave, Tushar N
2011-01-11  8:52       ` [E1000-devel] " Chris Rankin
2011-01-11 20:59       ` Chris Rankin
2011-01-12 17:35         ` Eric Dumazet
2011-01-12 17:42           ` Chris Rankin [this message]
2011-01-12 17:48             ` [E1000-devel] " Eric Dumazet
2011-01-12 18:05           ` Brandeburg, Jesse
2011-01-12 18:14             ` Eric Dumazet
2011-01-12 23:27               ` Chris Rankin
2011-01-13  4:55                 ` Eric Dumazet
2011-01-13  9:00                   ` Chris Rankin
2011-01-13  9:05                     ` Eric Dumazet
2011-01-13  9:24                       ` Chris Rankin

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=247288.34804.qm@web121705.mail.ne1.yahoo.com \
    --to=rankincj@yahoo.com \
    --cc=davem@davemloft.net \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=eric.dumazet@gmail.com \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=tushar.n.dave@intel.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