Re: 2.6.9, 64bit, 4GB memory => panics ...
From: Adam Heath (doogie_at_debian.org)
Date: 12/05/04
- Previous message: Zwane Mwaikambo: "Re: [PATCH] NX: Fix noexec kernel parameter / x86_64"
- In reply to: Rudolf Usselmann: "Re: 2.6.9, 64bit, 4GB memory => panics ..."
- Next in thread: Rudolf Usselmann: "Re: 2.6.9, 64bit, 4GB memory => panics ..."
- Reply: Rudolf Usselmann: "Re: 2.6.9, 64bit, 4GB memory => panics ..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 5 Dec 2004 01:20:14 -0600 (CST) To: Rudolf Usselmann <rudi@asics.ws>
On Sun, 5 Dec 2004, Rudolf Usselmann wrote:
> int mem[10000];
> int i, n;
>
> for(i=0;i<2000;i++) {
> printf("Doing alloc %0d ...\n",i);
> mem[i] = (int)malloc(1024*1024*1024);
allocate a 1 gig block, but store it in an int array? That's wrong.
> if(mem[i] == NULL)
> printf("Malloc failed ...\n");
> else
> for(n=0;n<(1024*1024*1024);n=n+640) mem[i] = n;
You alter n, but then always only set mem[i], without varying i.
Your program is buggy, and memleaks.
Plus, the kernel uses overcommit by default, and since you aren't actually
touching the memory you are allocating, you are only limited by the address
space size allowed per process(depends on how you configured the kernel).
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Previous message: Zwane Mwaikambo: "Re: [PATCH] NX: Fix noexec kernel parameter / x86_64"
- In reply to: Rudolf Usselmann: "Re: 2.6.9, 64bit, 4GB memory => panics ..."
- Next in thread: Rudolf Usselmann: "Re: 2.6.9, 64bit, 4GB memory => panics ..."
- Reply: Rudolf Usselmann: "Re: 2.6.9, 64bit, 4GB memory => panics ..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
