On Tue, Feb 12, 2002 at 03:31:59PM -0600, Eric wrote:
> Ahh...this may be a solution. It looks like I could build it to not
> do mmap()s, but do malloc()s instead by using -DUSE_MALLOC (and maybe
> even link it against hoard to have a really nice malloc)
>
> However, it appears to be a total pai
Paul Mclachlan <[EMAIL PROTECTED]> writes:
> At :47 02 Feb 2002 -0600, Eric wrote:
>
>> Does anyone have any idea how to fix this? Would it be a big job
>> to fix it in the JVM?
>
> You could grab the source to 1.3.1 at:
>
> http://www.sun.com/software/communitysource/
>
> and edit
>
I have tried it with the 64GB PAE turned on...I don't belive it
changes these constants. It didn't help me.
eric.
On Tue, Feb 12, 2002 at 11:58:50AM -0800, Vladimir G Ivanovic wrote:
> Have you tried enabling CONFIG_HIGHMEM64G when building your kernel?
> With a 4GB VM space, the kernel occupie
Ahh...this may be a solution. It looks like I could build it to not
do mmap()s, but do malloc()s instead by using -DUSE_MALLOC (and maybe
even link it against hoard to have a really nice malloc)
However, it appears to be a total pain to get this thing to compile...
I have no idea where a JDK wit
Have you tried enabling CONFIG_HIGHMEM64G when building your kernel?
With a 4GB VM space, the kernel occupies 1 GB and processes 3GB as
defined by TASK_SIZE:
page.h:81:#define __PAGE_OFFSET (0xC000)
page.h:120:#define PAGE_OFFSET((unsigned long)__PAGE_OFFSET)
At :47 02 Feb 2002 -0600, Eric wrote:
> Does anyone have any idea how to fix this? Would it be a big job to
> fix it in the JVM?
You could grab the source to 1.3.1 at:
http://www.sun.com/software/communitysource/
and edit
jdk131src/j2sdk1.3.1/src/solaris/hpi/src/memory_md.c
