From: Mike Galbraith <mikeg@wen-online.de>
To: Shawn Starr <spstarr@sh0n.net>
Cc: lkm <linux-kernel@vger.kernel.org>
Subject: Re: [ANOMALIES]: 2.4.2 - __alloc_pages: failed - Patch failed
Date: Sun, 25 Feb 2001 09:03:54 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.33.0102250848340.2015-100000@mikeg.weiden.de> (raw)
In-Reply-To: <3A98A7C9.B7F512DD@sh0n.net>
The way sg_low_malloc() tries to allocate, failure messages are
pretty much garanteed. It tries high order allocations (which
are unreliable even when not stressed) and backs off until it
succeeds.
In other words, the messages are a red herring.
-Mike
next prev parent reply other threads:[~2001-02-25 8:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0102250725180.1864-100000@mikeg.weiden.de>
2001-02-25 6:35 ` [ANOMALIES]: 2.4.2 - __alloc_pages: failed - Patch failed Shawn Starr
2001-02-25 8:03 ` Mike Galbraith [this message]
2001-02-25 23:13 ` Shawn Starr
2001-02-26 3:42 ` Marcelo Tosatti
2001-02-26 9:26 ` Alan Cox
2001-02-26 10:24 ` Marcelo Tosatti
2001-02-27 2:19 ` [ANOMALIES]: 2.4.2 - __alloc_pages: failed - Causes more then just msgs Shawn Starr
2001-02-27 10:08 ` Mike Galbraith
2001-02-27 21:52 ` Shawn Starr
2001-02-28 5:25 ` Mike Galbraith
[not found] <Pine.LNX.4.33.0102231409010.496-100000@mikeg.weiden.de>
2001-02-23 21:11 ` [ANOMALIES]: 2.4.2 - __alloc_pages: failed & mount hanging withloop device issues Shawn Starr
2001-02-24 2:18 ` [ANOMALIES]: 2.4.2 - __alloc_pages: failed - Patch failed Shawn Starr
2001-02-24 16:01 ` Marcelo Tosatti
2001-02-24 22:31 ` Shawn Starr
2001-02-24 21:43 ` Arnaldo Carvalho de Melo
2001-02-25 5:36 ` Mike Galbraith
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=Pine.LNX.4.33.0102250848340.2015-100000@mikeg.weiden.de \
--to=mikeg@wen-online.de \
--cc=linux-kernel@vger.kernel.org \
--cc=spstarr@sh0n.net \
/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;
as well as URLs for NNTP newsgroup(s).