Re: HIMEM calculation

2007-09-04 Thread Chris Snook
James Georgas wrote: > That's the vmalloc address space. You only get 896 MB in the NORMAL > zone on i386, to leave room for vmalloc. If you don't like it, go 64-bit. > > -- Chris I like it fine. I just didn't understand it. Thanks for answering. So, basically, the vmalloc

Re: HIMEM calculation

2007-09-04 Thread Chris Snook
James Georgas wrote: That's the vmalloc address space. You only get 896 MB in the NORMAL zone on i386, to leave room for vmalloc. If you don't like it, go 64-bit. -- Chris I like it fine. I just didn't understand it. Thanks for answering. So, basically, the vmalloc address

Re: HIMEM calculation

2007-09-03 Thread Chris Snook
James C. Georgas wrote: I'm not sure I understand how the kernel calculates the amount of physical RAM it can map during the boot process. I've quoted two blocks of kernel messages below, one for a kernel with NOHIGHMEM and another for a kernel with HIGHMEM4G. If I do the math on the BIOS

HIMEM calculation

2007-09-03 Thread James C. Georgas
I'm not sure I understand how the kernel calculates the amount of physical RAM it can map during the boot process. I've quoted two blocks of kernel messages below, one for a kernel with NOHIGHMEM and another for a kernel with HIGHMEM4G. If I do the math on the BIOS provided physical RAM map,

HIMEM calculation

2007-09-03 Thread James C. Georgas
I'm not sure I understand how the kernel calculates the amount of physical RAM it can map during the boot process. I've quoted two blocks of kernel messages below, one for a kernel with NOHIGHMEM and another for a kernel with HIGHMEM4G. If I do the math on the BIOS provided physical RAM map,

Re: HIMEM calculation

2007-09-03 Thread Chris Snook
James C. Georgas wrote: I'm not sure I understand how the kernel calculates the amount of physical RAM it can map during the boot process. I've quoted two blocks of kernel messages below, one for a kernel with NOHIGHMEM and another for a kernel with HIGHMEM4G. If I do the math on the BIOS