From: Stephan von Krawczynski <skraw@ithnet.com>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Memory Problem in 2.4.10-pre2 / __alloc_pages failed
Date: Fri, 31 Aug 2001 13:06:18 +0200 [thread overview]
Message-ID: <20010831130618.0d3b4b4c.skraw@ithnet.com> (raw)
In-Reply-To: <20010829232929Z16206-32383+2351@humbolt.nl.linux.org>
In-Reply-To: <20010829140706.3fcb735c.skraw@ithnet.com> <20010829232929Z16206-32383+2351@humbolt.nl.linux.org>
On Thu, 30 Aug 2001 01:36:10 +0200
Daniel Phillips <phillips@bonn-fries.net> wrote:
> [...]
> Let's try another way of dealing with it. What I'm trying to do with the
> patch below is leave a small reserve of 1/12 of pages->min, above the
> emergency reserve, to be consumed by non-PF_MEMALLOC atomic allocators.
> Please bear in mind this is completely untested, but would you try it
> please and see if the failure frequency goes down?
>
> --- ../2.4.9.clean/mm/page_alloc.c Thu Aug 16 12:43:02 2001
> +++ ./mm/page_alloc.c Wed Aug 29 23:47:39 2001
> @@ -493,6 +493,9 @@
> }
>
> /* XXX: is pages_min/4 a good amount to reserve for this? */
> + if (z->free_pages < z->pages_min / 3 && (gfp_mask & __GFP_WAIT) &&
> + !(current->flags & PF_MEMALLOC))
> + continue;
> if (z->free_pages < z->pages_min / 4 &&
> !(current->flags & PF_MEMALLOC))
> continue;
>
Hello Daniel,
I tried this patch and it makes _no_ difference. Failures show up in same situation and amount. Do you need traces? They look the same
Regards,
Stephan
next prev parent reply other threads:[~2001-08-31 11:07 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-29 12:07 Memory Problem in 2.4.10-pre2 / __alloc_pages failed Stephan von Krawczynski
2001-08-29 16:47 ` Roger Larsson
2001-08-29 19:18 ` Stephan von Krawczynski
[not found] ` <Pine.LNX.4.33.0108300521280.448-100000@mikeg.weiden.de>
2001-08-30 14:16 ` Stephan von Krawczynski
2001-08-29 23:36 ` Daniel Phillips
2001-08-30 14:46 ` Stephan von Krawczynski
2001-08-30 18:02 ` Daniel Phillips
2001-08-31 10:32 ` Stephan von Krawczynski
2001-08-30 23:53 ` [PATCH] __alloc_pages cleanup -R6 Was: " Roger Larsson
2001-08-31 7:43 ` Russell King
2001-08-31 23:22 ` Roger Larsson
2001-08-30 16:49 ` Roger Larsson
2001-08-31 11:06 ` Stephan von Krawczynski [this message]
2001-08-31 19:03 ` Daniel Phillips
-- strict thread matches above, loose matches on Subject: below --
2001-09-01 18:28 Stephan von Krawczynski
2001-09-02 1:57 ` Daniel Phillips
2001-09-02 2:21 ` Roger Larsson
2001-09-02 4:16 ` Daniel Phillips
2001-09-02 13:48 ` Alex Bligh - linux-kernel
2001-09-02 18:26 ` Daniel Phillips
2001-09-02 19:32 ` Alex Bligh - linux-kernel
2001-09-02 20:24 ` Daniel Phillips
2001-09-02 21:03 ` Alex Bligh - linux-kernel
2001-09-02 20:33 ` Daniel Phillips
2001-09-02 21:14 ` Alex Bligh - linux-kernel
2001-09-02 21:23 ` Daniel Phillips
2001-09-02 21:28 ` Alex Bligh - linux-kernel
[not found] <20010901055634Z16057-32383+2785@humbolt.nl.linux.org>
[not found] ` <Pine.LNX.4.33.0109011021570.280-100000@mikeg.weiden.de>
2001-09-01 18:54 ` Stephan von Krawczynski
2001-09-02 3:21 ` Mike Galbraith
[not found] <20010907154801.028a48e8.skraw@ithnet.com>
[not found] ` <689208719.999883299@[10.132.112.53]>
2001-09-07 21:13 ` Stephan von Krawczynski
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=20010831130618.0d3b4b4c.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@bonn-fries.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