From: Shawn Starr <spstarr@sh0n.net>
To: Mike Galbraith <mikeg@wen-online.de>
Cc: lkm <linux-kernel@vger.kernel.org>
Subject: Re: [ANOMALIES]: 2.4.2 - __alloc_pages: failed & mount hanging withloop device issues
Date: Fri, 23 Feb 2001 16:11:22 -0500 [thread overview]
Message-ID: <3A96D1F9.7EA6BBB6@sh0n.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0102231409010.496-100000@mikeg.weiden.de>
Ok apply patch and loop patch... I'll let you know what happens in my next
email.
Mike Galbraith wrote:
> On Fri, 23 Feb 2001, Shawn Starr wrote:
>
> > Feb 23 03:31:18 coredump kernel: __alloc_pages: 3-order allocation
> > failed.
> > Feb 23 03:31:18 coredump kernel: __alloc_pages: 3-order allocation
> > failed.
> > Feb 23 03:31:18 coredump kernel: __alloc_pages: 2-order allocation
> > failed.
> > Feb 23 03:31:18 coredump kernel: __alloc_pages: 3-order allocation
> > failed.
> > Feb 23 03:31:18 coredump kernel: __alloc_pages: 3-order allocation
> > failed.
> > Feb 23 03:31:18 coredump kernel: __alloc_pages: 2-order allocation
> > failed.
> > Feb 23 03:31:18 coredump kernel: __alloc_pages: 3-order allocation
> > failed.
> >
> > The use of mkisofs and xcdroster with cdrecord seems to cause this fault
> > in kernel.log
>
> Hi,
>
> Can you try the below for the high order allocation problem? We don't
> try very hard at all to service high order allocations under load. If
> it helps, let me know and I'll submit it to Rik for consideration.
>
> (for loop troubles, you should try Jens' latest loop patch located in
> your favorite kernel mirror under pub/linux/kernel/people/axboe)
>
> -Mike
>
> (patch was done against 2.4.1-ac20, but should go in ok)
> --- mm/page_alloc.c.org Fri Feb 23 13:21:54 2001
> +++ mm/page_alloc.c Fri Feb 23 13:28:33 2001
> @@ -274,7 +274,7 @@
> struct page * __alloc_pages(zonelist_t *zonelist, unsigned long order)
> {
> zone_t **zone;
> - int direct_reclaim = 0;
> + int direct_reclaim = 0, loop = 0;
> unsigned int gfp_mask = zonelist->gfp_mask;
> struct page * page;
>
> @@ -366,7 +366,7 @@
> * able to free some memory we can't free ourselves
> */
> wakeup_kswapd();
> - if (gfp_mask & __GFP_WAIT) {
> + if (gfp_mask & __GFP_WAIT && loop) {
> __set_current_state(TASK_RUNNING);
> current->policy |= SCHED_YIELD;
> schedule();
> @@ -393,6 +393,7 @@
> * --> try to free pages ourselves with page_launder
> */
> if (!(current->flags & PF_MEMALLOC)) {
> + loop++;
> /*
> * Are we dealing with a higher order allocation?
> *
> @@ -440,7 +441,7 @@
> memory_pressure++;
> try_to_free_pages(gfp_mask);
> wakeup_bdflush(0);
> - if (!order)
> + if (!order || loop < (1 << order))
> goto try_again;
> }
> }
next parent reply other threads:[~2001-02-23 21:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0102231409010.496-100000@mikeg.weiden.de>
2001-02-23 21:11 ` Shawn Starr [this message]
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 1:03 ` [ANOMALIES]: 2.4.2 - __alloc_pages: ksysoops debug info Shawn Starr
2001-02-25 5:36 ` [ANOMALIES]: 2.4.2 - __alloc_pages: failed - Patch failed Mike Galbraith
2001-02-24 2:25 ` [ANOMALIES]: 2.4.2 - __alloc_pages: failed & mount hanging withloop device issues Rik van Riel
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=3A96D1F9.7EA6BBB6@sh0n.net \
--to=spstarr@sh0n.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mikeg@wen-online.de \
/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