mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: Szabolcs Szakacsits <szaka@f-secure.com>
Cc: Feng Xian <fxian@fxian.jukie.net>,
	linux-kernel@vger.kernel.org, Feng Xian <fxian@chrysalis-its.com>
Subject: Re: __alloc_pages: 4-order allocation failed
Date: Thu, 26 Apr 2001 11:33:03 -0600	[thread overview]
Message-ID: <20010426113303.A16399@vger.timpanogas.org> (raw)
In-Reply-To: <20010426001539.A14115@vger.timpanogas.org> <Pine.LNX.4.30.0104261942160.16238-100000@fs131-224.f-secure.com>
In-Reply-To: <Pine.LNX.4.30.0104261942160.16238-100000@fs131-224.f-secure.com>; from szaka@f-secure.com on Thu, Apr 26, 2001 at 08:00:12PM +0200

On Thu, Apr 26, 2001 at 08:00:12PM +0200, Szabolcs Szakacsits wrote:
> 
> On Thu, 26 Apr 2001, Jeff V. Merkey wrote:

The request should fail after two or three attempts rather than hang
the entire system waiting for memory.

Jeff

> 
> > I am seeing this as well on 2.4.3 with both _get_free_pages() and
> > kmalloc().  In the kmalloc case, the modules hang waiting
> > for memory.
> 
> One possible source of this hang is due to the change below in
> 2.4.3, non GPF_ATOMIC and non-recursive allocations (PF_MEMALLOC is set)
> will loop until the requested continuous memory is available.
> 
> 	Szaka
> 
> diff -u --recursive --new-file v2.4.2/linux/mm/page_alloc.c
> linux/mm/page_alloc.c--- v2.4.2/linux/mm/page_alloc.c        Sat Feb  3
> 19:51:32 2001
> +++ linux/mm/page_alloc.c       Tue Mar 20 15:05:46 2001
> @@ -455,8 +455,7 @@
>                         memory_pressure++;
>                         try_to_free_pages(gfp_mask);
>                         wakeup_bdflush(0);
> -                       if (!order)
> -                               goto try_again;
> +                       goto try_again;
>                 }
>         }
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2001-04-26 17:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-26  1:09 Feng Xian
2001-04-26  1:48 ` Marcelo Tosatti
2001-04-26 12:09   ` Feng Xian
2001-04-26 12:30     ` Andi Kleen
2001-04-26 13:50       ` Feng Xian
2001-04-26 13:53         ` Andi Kleen
2001-04-26 13:56         ` Feng Xian
2001-04-26  6:15 ` Jeff V. Merkey
2001-04-26  8:57   ` Mike Galbraith
2001-04-26 18:00   ` Szabolcs Szakacsits
2001-04-26 17:33     ` Jeff V. Merkey [this message]
     [not found] <Pine.LNX.4.10.10104252238590.3810-100000@coffee.psychology.mcmaster.ca>
2001-04-26 12:11 ` Feng Xian
2001-07-02 16:59 Ho Chak Hung
2001-07-05 21:25 ` Jes Sorensen
2001-07-06  0:33 David Whysong
2001-07-06  0:23 ` Marcelo Tosatti

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=20010426113303.A16399@vger.timpanogas.org \
    --to=jmerkey@vger.timpanogas.org \
    --cc=fxian@chrysalis-its.com \
    --cc=fxian@fxian.jukie.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=szaka@f-secure.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

all inboxes | Powered by JetHome®