From: Grzegorz Piotr Jaskiewicz <gj@pointblue.com.pl>
To: ncunningham@linuxmail.com
Cc: Pavel Machek <pavel@ucw.cz>, kernel list <linux-kernel@vger.kernel.org>
Subject: Re: swsusp: fix error handling in "not enough swap space"
Date: Sat, 24 Apr 2004 05:45:25 +0100 [thread overview]
Message-ID: <4089F0E5.3050006@pointblue.com.pl> (raw)
In-Reply-To: <opr6x0o10uruvnp2@laptop-linux.wpcb.org.au>
[-- Attachment #1: Type: text/plain, Size: 750 bytes --]
Nigel Cunningham wrote:
> Hmm.
>
> I agree with you; it does sound like the process of eating memory is
> grabbing all the swap. I can't see how it could be doing that,
> however. If you really want to use Pavel's version, I'd suggest
> adding some more debug statements. Perhaps print out the number of
> swap pages free at the start of that loop.
>
Ok, now funny bit happends. Simple program like that:
while(1){
char *a=malloc(1024*1024*16);
if (a==NULL)
break;
}
can allocate only about 200MB, than exits. That's the fist thing.
Second one, starting KDE, and when swap usage != 0 (just to be sure
there is no problem with any assumption), gives me loads of error
messages (see attached file).
Very bizzare behavior.
[-- Attachment #2: syslog.bz2 --]
[-- Type: application/octet-stream, Size: 3731 bytes --]
next prev parent reply other threads:[~2004-04-24 4:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-24 3:17 swsusp: fix error handling in "not enough swap space" Grzegorz Piotr Jaskiewicz
2004-04-24 3:27 ` Nigel Cunningham
2004-04-24 4:04 ` Grzegorz Piotr Jaskiewicz
2004-04-24 4:13 ` Nigel Cunningham
2004-04-24 4:45 ` Grzegorz Piotr Jaskiewicz [this message]
2004-04-24 18:35 ` Pavel Machek
2004-04-25 6:48 ` Grzegorz Piotr Jaskiewicz
2004-04-25 20:46 ` Pavel Machek
2004-04-25 8:51 ` Grzegorz Piotr Jaskiewicz
2004-04-25 20:45 ` Pavel Machek
2004-04-26 20:22 ` Grzegorz Piotr Jaskiewicz
2004-04-26 20:32 ` Pavel Machek
[not found] ` <408D7555.1000607@pointblue.com.pl>
2004-04-26 20:54 ` Pavel Machek
2004-04-24 18:32 ` Pavel Machek
2004-04-25 2:53 ` Grzegorz Piotr Jaskiewicz
-- strict thread matches above, loose matches on Subject: below --
2004-02-29 13:04 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=4089F0E5.3050006@pointblue.com.pl \
--to=gj@pointblue.com.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@linuxmail.com \
--cc=pavel@ucw.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.