From: "Gabriel.Leen" <Gabriel.Leen@ul.ie>
To: Benjamin LaHaise <bcrl@redhat.com>,
"'ebiederm@xmission.com'" <ebiederm@xmission.com>,
"'tvignaud@mandrakesoft.com'" <tvignaud@mandrakesoft.com>
Cc: "Gabriel.Leen" <gabriel.leen@ul.ie>,
"'linux-mm@kvack.org'" <linux-mm@kvack.org>,
"'brian@worldcontrol.com'" <brian@worldcontrol.com>,
"'arjan@fenrus.demon.nl'" <arjan@fenrus.demon.nl>
Subject: RE: Process not given >890MB on a 4MB machine ?????????
Date: Fri, 21 Sep 2001 17:07:34 +0100 [thread overview]
Message-ID: <5D2F375D116BD111844C00609763076E050D1658@exch-staff1.ul.ie> (raw)
Hello everybody,
Thanks for your help.
Unfortunately the package which I am using is a pre-compiled distribution,
so that limits what I can do with it :(
But I will hasle the developers and see what version of glibc they used.
QUESTION:
Have you actualy run a single process on the rawhide distribution which uses
~3GB ????????????
Please say YES :)
Red Hat kernel 2.4.9 as in 2.4.9-0.5 from rawhide ?
It should work, you should be able to get close to 3Gb....
++++++++++++++++++++++++++++++++++++++++++++++++++++
Some more info:
I have a small program listing attached which has helped me to identify the
problem.
It just gobbles up memory and writes zeros and f's to it
When I ran this on the kernel distribution out of the Box for Linux 7.1
delux
it would only work up to 1.2GB and then malloc returned NULL, continue
writing the
error messages to the console and eventually terminate normally.
Then I compiled the 2.4.9 kernel with the patch from Alan and it will run up
to 2GB
but not more, now the error occurs straight away when I hit run:
"segmentation fault"
Previously on the older kernel it would run when malloc returned NULL, the
program
continued writing the error and terminated normally.
Now the kernel appears to be psychic or something ?
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Thank you again for your help, much appreciated,
Gabriel
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
#include <stdlib.h>
// Change SIZE for experiments
// size in MegaBytes.
#define SIZE 300
// Memory is allocated in SIZE blocks of allocation units.
// currently all allocation units are stored in one array.
#define DEFAULT_BLOCK 1024
#define ALLOCATION_UNIT 1024
int main() {
int c, i,j;
char *ch;
char *charray[SIZE*DEFAULT_BLOCK];
for( i = 0; i < SIZE; i++ ) {
for( c = 0; c < DEFAULT_BLOCK; c++ ) {
ch = malloc(ALLOCATION_UNIT);
if( ch == NULL )
printf("%d FAILED", c);
charray[(i*DEFAULT_BLOCK)+c]=ch;
}
printf("%d\n", i);
if( i % 10 == 0 )
sleep(1);
}
printf("writing 0x00-s to memory ...\n");
for( i = 0; i < SIZE; i++ ) {
for( c = 0; c < DEFAULT_BLOCK; c++ ) {
ch=charray[(i*DEFAULT_BLOCK)+c];
for(j=0;j<ALLOCATION_UNIT;j++) {
ch[j]=0x00;
}
}
printf("%d\n", i);
if( i % 10 == 0 )
sleep(1);
}
printf("writing 0xFF-s to memory ...\n");
for( i = 0; i < SIZE; i++ ) {
for( c = 0; c < DEFAULT_BLOCK; c++ ) {
ch=charray[(i*DEFAULT_BLOCK)+c];
for(j=0;j<ALLOCATION_UNIT;j++) {
ch[j]=0xFF;
}
}
printf("%d\n", i);
if( i % 10 == 0 )
sleep(1);
}
printf("Memory allocation succeeded. Total allocated memory in
kilobytes = %d\n",\
((DEFAULT_BLOCK*SIZE*ALLOCATION_UNIT)+sizeof(charray))/1024);
printf("sleeping for 30 seconds ...\n");
sleep(30);
return 0;
}
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
END
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next reply other threads:[~2001-09-21 16:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-21 16:07 Gabriel.Leen [this message]
2001-09-22 2:01 ` Rik van Riel
[not found] <5D2F375D116BD111844C00609763076E050D1681@exch-staff1.ul.ie>
2001-09-24 22:49 ` Rik van Riel
-- strict thread matches above, loose matches on Subject: below --
2001-09-24 22:41 Gabriel.Leen
2001-09-24 21:16 ` Joseph A Knapka
2001-09-25 10:59 ` Stephen C. Tweedie
2001-09-25 17:36 ` afei
2001-09-26 7:04 ` Eric W. Biederman
2001-09-26 8:53 ` Stephen C. Tweedie
2001-09-24 21:15 Gabriel.Leen
2001-09-24 22:16 ` Jonathan Morton
2001-09-20 19:25 Gabriel.Leen
2001-09-20 19:56 ` brian
2001-09-20 20:36 ` Thierry Vignaud
2001-09-20 20:56 ` Benjamin LaHaise
2001-09-21 8:29 ` Eric W. Biederman
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=5D2F375D116BD111844C00609763076E050D1658@exch-staff1.ul.ie \
--to=gabriel.leen@ul.ie \
--cc=arjan@fenrus.demon.nl \
--cc=bcrl@redhat.com \
--cc=brian@worldcontrol.com \
--cc=ebiederm@xmission.com \
--cc=linux-mm@kvack.org \
--cc=tvignaud@mandrakesoft.com \
/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