SEO

Could you tell me what is the maximum RAM, slakware can manage, and
what would be the max heap that could be given to a java program? Thx

Ted <jeanmorin3@gmail.com> wrote:
> Could you tell me what is the maximum RAM, slakware can manage, and
> what would be the max heap that could be given to a java program? Thx

A Slackware 12.* default kernel has highmem support which means that it
supports up to 4 GB of RAM. However, a single process can not user more
than 2 GB with this memory model. Also note that even though the kernel
supports up to 4 GB many motherboards use some of that address space for
peripherals you you won't be able to see more than something like 3.5 GB.

If you want to use more RAM than that you will have to compile a custom
kernel with PAE support or use a 64 bit distribution instead.

regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc3(at)poolhem.se Examples of addresses which go to spammers:
root@localhost postmaster@localhost

On Fri, 09 May 2008 07:58:41 +0200, Henrik Carlqvist wrote:

> Ted <jeanmorin3@gmail.com> wrote:
>> Could you tell me what is the maximum RAM, slakware can manage, and
>> what would be the max heap that could be given to a java program? Thx
>
> A Slackware 12.* default kernel has highmem support which means that it
> supports up to 4 GB of RAM. However, a single process can not user more
> than 2 GB with this memory model. Also note that even though the kernel
> supports up to 4 GB many motherboards use some of that address space for
> peripherals you you won't be able to see more than something like 3.5
> GB.
>
> If you want to use more RAM than that you will have to compile a custom
> kernel with PAE support or use a 64 bit distribution instead.

There are several choices for 64-bit builds of Slackware, of course.

Slamd and Bluewhite64 are easily found through Distrowatch and are
basically 64-bit rebuilds of (close to) vanilla Slackware.

On Thu, 08 May 2008 13:06:04 -0700, Ted wrote:

> Could you tell me what is the maximum RAM, slakware can manage, and what
> would be the max heap that could be given to a java program? Thx

"The main danger of running on a 32 bit system with lots of highmem (more
than 8GB) is that the kernel could end up needing to allocate more data
than what fits in ZONE_NORMAL. This means the machine can effectively run
out of memory, even if there were still lots of high memory free.

Another issue is that the system will more aggressively reclaim kernel
data structures like cached inodes, buffer heads and other caches that
can help system performance.

The third issue is that, on a 32 bit system, no process will be able to
effectively use more than 3GB of memory. This means that buying more than
4GB of memory is only useful if none of the processes on your system need
all of the memory.

For these reasons it is recommended that if you buy a system with more
than 4GB of memory, you should consider getting a 64 bit CPU and
installing a 64 bit operating system. The price difference between 32 and
64 bit systems is practically nonexistant in 2005, and 64 bit x86-64
systems can still run 32 bit applications, so there is no real need to
experience the pains of highmem any more... "

http://linux-mm.org/HighMemory

Also read these

http://www.spack.org/wiki/LinuxRamLimits
http://kerneltrap.org/node/2450

Richard James
--
sig fail on line -1

On May 9, 6:16*am, Richard James <rja...@invalid.com> wrote:
> On Thu, 08 May 2008 13:06:04 -0700, Ted wrote:
> > Could you tell me what is the maximum RAM, slakware can manage, and what
> > would be the max heap that could be given to a java program? *Thx
>
> "The main danger of running on a 32 bit system with lots of highmem (more
> than 8GB) is that the kernel could end up needing to allocate more data
> than what fits in ZONE_NORMAL. This means the machine can effectively run
> out of memory, even if there were still lots of high memory free.
>
> Another issue is that the system will more aggressively reclaim kernel
> data structures like cached inodes, buffer heads and other caches that
> can help system performance.
>
> The third issue is that, on a 32 bit system, no process will be able to
> effectively use more than 3GB of memory. This means that buying more than
> 4GB of memory is only useful if none of the processes on your system need
> all of the memory.
>
> For these reasons it is recommended that if you buy a system with more
> than 4GB of memory, you should consider getting a 64 bit CPU and
> installing a 64 bit operating system. The price difference between 32 and
> 64 bit systems is practically nonexistant in 2005, and 64 bit x86-64
> systems can still run 32 bit applications, so there is no real need to
> experience the pains of highmem any more... "
>
> http://linux-mm.org/HighMemory
>
> Also read these
>
> http://www.spack.org/wiki/LinuxRamLi....org/node/2450
>
> Richard James
> --
> sig fail on line -1

Thx Ted

Richard James wrote:
> On Thu, 08 May 2008 13:06:04 -0700, Ted wrote:
>
>> Could you tell me what is the maximum RAM, slakware can manage, and what
>> would be the max heap that could be given to a java program? Thx
>
> "The main danger of running on a 32 bit system with lots of highmem (more
> than 8GB) is that the kernel could end up needing to allocate more data
> than what fits in ZONE_NORMAL. This means the machine can effectively run
> out of memory, even if there were still lots of high memory free.
>
> Another issue is that the system will more aggressively reclaim kernel
> data structures like cached inodes, buffer heads and other caches that
> can help system performance.
>
> The third issue is that, on a 32 bit system, no process will be able to
> effectively use more than 3GB of memory. This means that buying more than
> 4GB of memory is only useful if none of the processes on your system need
> all of the memory.
>
> For these reasons it is recommended that if you buy a system with more
> than 4GB of memory, you should consider getting a 64 bit CPU and
> installing a 64 bit operating system. The price difference between 32 and
> 64 bit systems is practically nonexistant in 2005, and 64 bit x86-64
> systems can still run 32 bit applications, so there is no real need to
> experience the pains of highmem any more... "
>
> http://linux-mm.org/HighMemory
>
> Also read these
>
> http://www.spack.org/wiki/LinuxRamLimits
> http://kerneltrap.org/node/2450
>
> Richard James

just wondering can you still buy 32 bit only CPU's from intel or
amd these days ? iirc the whole c2duo line is 64bit