[Octave-patch-tracker] [patch #9924] Suggestion for a memory() function

[Lars Kindermann]

Follow-up Comment #15, patch #9924 (project octave):

32Bit systems with PAE can use up to 64GB of RAM, but every process is limited
to a virtual address space of 4GB, 1GB is typically assigned to the kernel,
3GB to the userspace. This user/kernel split is defined when compiling the
kernel, with the 3GB/1GB being the default:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/x86/Kconfig#n1410

So the RAM that is available to each octave process is limited by the total
RAM available on the system or the virtual address space left for the process,
whatever is smaller.

That's why I think the RAM available to the process is more important than the
free RAM on the system. I added that computation to a new version of memory.m,
so user.RamAvailableAllArrays and syst.PhysicalMemory.Available are different
now.

Maybe to avoid confusion, the field name could contain the term Octave, e.g.
RamAvailableOctave istead of RamAvailableAllArrays?



(file #48984)
    _______________________________________________________

Additional Item Attachment:

File name: memory.m                       Size:7 KB
    <https://savannah.gnu.org/file/memory.m?file_id=48984>



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/patch/?9924>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/