From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: marcelo@conectiva.com.br (Marcelo Tosatti)
Cc: mikeg@wen-online.de (Mike Galbraith),
torvalds@transmeta.com (Linus Torvalds),
spstarr@sh0n.net (Shawn Starr),
linux-kernel@vger.kernel.org (lkm)
Subject: Re: [ANOMALIES]: 2.4.2 - __alloc_pages: failed - Patch failed
Date: Mon, 26 Feb 2001 09:26:44 +0000 (GMT) [thread overview]
Message-ID: <E14XJvZ-0000rF-00@the-village.bc.nu> (raw)
In-Reply-To: <Pine.LNX.4.21.0102260029300.4659-100000@freak.distro.conectiva> from "Marcelo Tosatti" at Feb 26, 2001 12:42:38 AM
> We can add an allocation flag (__GFP_NO_CRITICAL?) which can be used by
> sg_low_malloc() (and other non critical allocations) to fail previously
> and not print the message.
It is just for debugging. The message can go. If anytbing it would be more
useful to tack Failed alloc data on the end of /proc/slabinfo
next prev parent reply other threads:[~2001-02-26 14:34 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
2001-02-25 23:13 ` Shawn Starr
2001-02-26 3:42 ` Marcelo Tosatti
2001-02-26 9:26 ` Alan Cox [this message]
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=E14XJvZ-0000rF-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=mikeg@wen-online.de \
--cc=spstarr@sh0n.net \
--cc=torvalds@transmeta.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;
as well as URLs for NNTP newsgroup(s).