From: Andrew Morton <akpm@osdl.org>
To: Pavel Machek <pavel@suse.cz>
Cc: rjw@sisk.pl, linux-kernel@vger.kernel.org, agruen@suse.de
Subject: Re: swsusp: 8-order memory allocations problem (was: Re: Fix random crashes in x86-64 swsusp)
Date: Sun, 10 Oct 2004 11:28:30 -0700 [thread overview]
Message-ID: <20041010112830.3c2996bf.akpm@osdl.org> (raw)
In-Reply-To: <20041010134846.GD19831@elf.ucw.cz>
Pavel Machek <pavel@suse.cz> wrote:
>
> > It's sort of strange, because there were 250 meg of RAM available, out of 500,
> > at that time.
>
> Well, you have 250MB free, but apparently not enough contignuous free pages...
>
> You may try this one, it may reduce probability of this kind of
> failure...
The chances of successfully finding 256 physically contiguous free
pages are small. A shrink_all_memory() pass will help of course,
but the chances of failure are still quite high.
Dunno - maybe alloc_pagedir() should use vmalloc()? That's a non-atomic
allocation but alloc_pagedir() really shouldn't be using GFP_ATOMIC anyway.
next prev parent reply other threads:[~2004-10-10 18:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 21:14 2.6.9-rc3[+recent swsusp patches]: swsusp kernel-preemption-unfriendly? Rafael J. Wysocki
2004-10-05 21:27 ` Pavel Machek
2004-10-06 8:55 ` Rafael J. Wysocki
2004-10-06 8:54 ` Pavel Machek
2004-10-06 10:06 ` Rafael J. Wysocki
2004-10-06 10:12 ` Pavel Machek
2004-10-06 21:46 ` Rafael J. Wysocki
2004-10-06 22:06 ` Fix random crashes in x86-64 swsusp Pavel Machek
2004-10-06 22:13 ` [kernel] " Andi Kleen
2004-10-06 22:25 ` Andrew Morton
2004-10-06 22:24 ` Pavel Machek
2004-10-08 20:59 ` swsusp: 8-order memory allocations problem (was: Re: Fix random crashes in x86-64 swsusp) Rafael J. Wysocki
2004-10-10 13:48 ` Pavel Machek
2004-10-10 18:28 ` Andrew Morton [this message]
2004-10-13 17:24 ` Rafael J. Wysocki
2004-10-14 15:37 ` swsusp: 8-order memory allocations problem (update) Rafael J. Wysocki
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=20041010112830.3c2996bf.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=agruen@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=rjw@sisk.pl \
/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