Re: Linux sees only 4 GB out of 8



Pascal Hambourg <boite-a-spam@xxxxxxxxxxxxxxx> wrote:
[...] per-process virtual memory space is still limited to 4
GiB. However AFAIK this limit is not involved in the swap use reported
by Stefan.

Mmm, ok; I didn't read it that way.

If you've a per-process 4 GiB limit and a system with more that 4 GiB
memory, then the swapper would only kick in if the system itself was
needing swap. In which case it doesn't matter whether you're running
32-bit PAE or true 64-bit. The per-process limit simply prevents the
application growing beyond that fixed limit.

Chris
.



Relevant Pages

  • Re: Whats up with the swapping since 10/stable
    ... Things seems to need swap although there is still available memory. ... Real Installed: 8.00 GiB ... Actual Hit Ratio: 73.81% 3.09m ...
    (freebsd-stable)
  • Re: Linux-Swap Partition - General Question
    ... No, seriously, it all depends on how often you hit swap. ... PCI devices are accessed by way of RAM ... RAM you have above ~3.3 GiB will get obscured by the PCI address space. ... obscured by the PCI memory hole. ...
    (alt.os.linux)
  • Re: Time to bump default VM_SWZONE_SIZE_MAX?
    ... should be approximately 9 MiB per GiB of swap space. ... By default, struct swblock is 288 ... 9GB swap. ...
    (freebsd-current)
  • Re: Time to bump default VM_SWZONE_SIZE_MAX?
    ... be approximately 9 MiB per GiB of swap space. ... this is 2.25 MiB per GiB. ... you can't fully populate each swblock. ...
    (freebsd-current)
  • Re: size of swapped-out part of the process
    ... Hence (VmSize - VmRSS) is far from being swapped-out part of the ... Doesn't top's SWAP field give you this? ... Per-process participation in swap. ... 'top' naively shows (VmSize - VmRSS) in the SWAP column, ...
    (Linux-Kernel)