linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Starr <spstarr@sh0n.net>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Mike Galbraith <mikeg@wen-online.de>,
	Linus Torvalds <torvalds@transmeta.com>,
	lkm <linux-kernel@vger.kernel.org>
Subject: Re: [ANOMALIES]: 2.4.2 - __alloc_pages: failed - Causes more then just  msgs
Date: Mon, 26 Feb 2001 21:19:43 -0500	[thread overview]
Message-ID: <3A9B0EBE.BBC54F1@sh0n.net> (raw)
In-Reply-To: <Pine.LNX.4.21.0102260610030.5276-100000@freak.distro.conectiva>

It may not be an important message but what does happen is /dev/dsp becomes
hung and no sound works after the fault. So something is definately wrong.

Shawn.

Marcelo Tosatti wrote:

> On Mon, 26 Feb 2001, Alan Cox wrote:
>
> > > 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
>
> The issue is not the warn message.
>
> Non critical allocations (such as this case of sg_low_malloc()) are trying
> to get additional memory to optimize things -- we want the allocator to be
> lazy and fail previously instead doing hard work. If kswapd cannot keep up
> with the memory pressure, we're surely in a memory shortage state.
>
> Its better to get out of the memory shortage instead running into OOM
> because of some optimization, I guess.
>
> Another example of such a flag is swapin readahead.

--
Hugged a Tux today? (tm)




  reply	other threads:[~2001-02-27  2:20 UTC|newest]

Thread overview: 10+ 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
2001-02-26 10:24         ` Marcelo Tosatti
2001-02-27  2:19           ` Shawn Starr [this message]
2001-02-27 10:08             ` [ANOMALIES]: 2.4.2 - __alloc_pages: failed - Causes more then just msgs Mike Galbraith
2001-02-27 21:52               ` Shawn Starr
2001-02-28  5:25                 ` 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=3A9B0EBE.BBC54F1@sh0n.net \
    --to=spstarr@sh0n.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=mikeg@wen-online.de \
    --cc=shawn@rhua.org \
    --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).