From: Pascal Schmidt <pascal.schmidt@email.de>
To: ncunningham@linuxmail.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.9-rc2-mm1 swsusp bug report.
Date: Sat, 25 Sep 2004 03:05:40 +0200 [thread overview]
Message-ID: <E1CB10O-0000HL-FJ@localhost> (raw)
In-Reply-To: <2I7Zd-1TK-11@gated-at.bofh.it>
On Sat, 25 Sep 2004 01:50:08 +0200, you wrote in linux.kernel:
> The problem isn't really that you're out of memory. Rather, the memory
> is so fragmented that swsusp is unable to get an order 8 allocation in
> which to store its metadata. There isn't really anything you can do to
> avoid this issue apart from eating memory (which swsusp is doing
> anyway).
That's one megabyte, right? Can't we preallocate that on boot, while
there's still chance to get that much contiguous memory? If the
user has swsusp compiled into his kernel, he probably wants it to
function, so it's not really "wasted".
--
Ciao,
Pascal
next parent reply other threads:[~2004-09-25 1:06 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2HO0C-4xh-29@gated-at.bofh.it>
[not found] ` <2I5b2-88s-15@gated-at.bofh.it>
[not found] ` <2I5E5-6h-19@gated-at.bofh.it>
[not found] ` <2I7Zd-1TK-11@gated-at.bofh.it>
2004-09-25 1:05 ` Pascal Schmidt [this message]
2004-09-25 10:16 ` 2.6.9-rc2-mm1 swsusp bug report Pavel Machek
2004-10-10 18:17 ` Jan Rychter
2004-10-11 13:32 ` Pavel Machek
2004-10-11 14:53 ` Jan Rychter
2004-10-17 19:10 ` Pavel Machek
2004-10-17 21:40 ` Nigel Cunningham
2004-10-11 9:56 ` Stefan Seyfried
2004-10-11 14:59 ` Pavel Machek
2004-10-11 17:18 ` Stefan Seyfried
2004-10-11 19:58 ` Rafael J. Wysocki
2004-10-12 8:55 ` Pavel Machek
2004-10-13 17:29 ` Rafael J. Wysocki
2004-10-14 21:47 ` swsusp: 8-order allocation failure on demand (was: Re: 2.6.9-rc2-mm1 swsusp bug report.) Rafael J. Wysocki
2004-10-14 21:54 ` swsusp: 8-order allocation failure on demand (update) Rafael J. Wysocki
2004-10-16 16:43 ` Pavel Machek
2004-10-16 19:31 ` Rafael J. Wysocki
2004-10-16 20:40 ` Pavel Machek
2004-10-16 21:05 ` Rafael J. Wysocki
2004-10-16 21:25 ` Pavel Machek
2004-09-24 2:19 2.6.9-rc2-mm1 swsusp bug report Kevin Fenzi
2004-09-24 14:37 ` Pavel Machek
2004-09-24 21:09 ` Kevin Fenzi
2004-09-24 23:40 ` Nigel Cunningham
2004-09-25 1:45 ` Kevin Fenzi
2004-09-25 11:53 ` Nigel Cunningham
2004-09-25 12:22 ` Nick Piggin
2004-09-25 12:56 ` William Lee Irwin III
2004-09-25 13:21 ` Nigel Cunningham
2004-09-25 12:56 ` Nigel Cunningham
2004-09-25 13:38 ` Nick Piggin
2004-09-25 13:03 ` Nigel Cunningham
2004-09-25 15:45 ` Pavel Machek
2004-09-25 22:03 ` Nigel Cunningham
2004-09-26 10:04 ` Pavel Machek
2004-09-26 21:59 ` Nigel Cunningham
2004-09-26 22:43 ` Pavel Machek
2004-09-27 10:12 ` Nigel Cunningham
2004-09-26 16:18 ` Marcelo Tosatti
2004-09-26 18:39 ` Pavel Machek
2004-09-25 10:15 ` Pavel Machek
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=E1CB10O-0000HL-FJ@localhost \
--to=pascal.schmidt@email.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@linuxmail.org \
/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