From: "Ivan Stepnikov" <iv@spylog.com>
To: <linux-kernel@vger.kernel.org>
Subject: Kernel is unstable
Date: Thu, 1 Mar 2001 12:16:08 +0300 [thread overview]
Message-ID: <001701c0a230$40e12240$0e04a8c0@iv> (raw)
Hello!
I tried to test linux memory allocation. For experiment I used i386
architecture with Pentium III processor, 512M RAM and 8G swap space. For
memory allocation libhoard was tried. Linux kernel 2.4.2 with patch
per-process-3.5G-IA32-no-PAE-1, at
/pub/linux/kernel/people/andrea/patches/v2.4/2.4.0-test11-pre5/ on
ftp.kernel.org (This patch should force memory allocation for one process up
to 3.5G approximately).
When I try large blocks (about 256K - 1M) everything was ok. More then 3G
memory was successfully allocated.
On small blocks result was significantly worse. About 2.3 - 2.4G was
allocated and system hanged. But it was possible to switch between local
consoles, and to receive ping replay by network. Actually it's only one sign
of life (hard disk didn't work and it was impossible to reboot the machine
by correct methods). At /var/log/messages was
Feb 28 17:08:55 zetta kernel: <ed.
Feb 28 17:08:55 zetta kernel: __alloc_pages: 0-order allocation failed.
Feb 28 17:09:05 zetta last message repeated 363 times
Test program looks like this:
block = 1024;
for (i=1; ; ++i ){
if(p==malloc(block)){
perror("failed");
fprintf(stderr,"Error! Size total:%uM pass:
%u\n",size/1024/1024,i);
return 0;
}
size += block;
printf("Size total:%uM pass: %u\n",size/1024/1024,i);
}
I think, this test shouldn't hang system. System may work slowly, very
slowly but it shouldn't hang. If system cannot allocate any pages it should
return correct value.
And the main thing: it seems the system doesn't use all available swap
space.
I'm sure if system works properly results must be other.
--
Regards,
Ivan Stepnikov.
next reply other threads:[~2001-03-01 9:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-01 9:16 Ivan Stepnikov [this message]
2001-03-01 10:27 ` Kernel is unstable Matti Aarnio
2001-03-01 14:35 ` Andrea Arcangeli
2001-03-01 14:39 ` Andrea Arcangeli
2001-03-01 18:20 ` Alan Cox
2001-03-01 18:30 ` Andrea Arcangeli
2001-03-01 19:04 ` David S. Miller
2001-03-01 20:45 ` Andrea Arcangeli
2001-03-01 19:12 ` Linus Torvalds
2001-03-02 8:23 ` Christoph Rohland
2001-03-02 8:40 ` David Howells
2001-03-02 14:01 ` Andrea Arcangeli
2001-03-02 17:52 ` Linus Torvalds
2001-03-05 23:06 ` Chris Wedgwood
2001-03-01 13:39 ` Richard B. Johnson
2001-03-01 14:24 ` Andrea Arcangeli
2001-03-01 17:12 ` Ingo Oeser
-- strict thread matches above, loose matches on Subject: below --
2001-03-01 13:55 Heusden, Folkert van
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='001701c0a230$40e12240$0e04a8c0@iv' \
--to=iv@spylog.com \
--cc=linux-kernel@vger.kernel.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