If your memory reservations exceed your backing store, the additional
reservations are being made against physical RAM. That means you
have physical memory that is not available for active use, either for
memory allocations or for things like file system buffering. I hesitate
to say that it makes
Hi David,
Thanks for the detailed reply. You said: "If your memory reservations exceed
the size of your backing store, you can have memory allocation failures while
still having lots of unallocated backing store."
In our case the swap device is 40GB in size. Does it mean we're likely to see
me
The space reported by "swap -l" refers to disk-based backing store, but
the swap values reported by "swap -s", "sar -r", vmstat, and top all refer
to available space in swapfs, which is the vnode interface between the
anon layer and physical swap devices. It is essentially virtual swap
space, and
