Quote:
Originally Posted by
achenle
Linux doesn't have "virtual swap", but by default Linux does overcommit swap space - IMO a REALLY, REALLY BAD IDEA.
I've heard it referred to as virtual swap, and took it as another term for it...
A gridlocked system with insufficient RAM for
kill -9 rameater is a tough nut to crack too, with the same fix as the oom-killer: "Don't let it happen". That's why there's programmable limits for these things.
I'll note that Linux systems tend to be poorly configured for swap in general, it's mostly considered a 'quick fix' for brief low-ram/high load conditions... It gets thrown on the same spindle and forgotten. So if it gets used at all, performance truly goes down the toilet.
Quote:
That wouldn't usually need swap space because the backing store for the virtual memory would be your hard disk you mmap()'d, but you could probably map it in such a way that if you were to write to it, the changed pages would require swap backing. Maybe by mmap()'ing a read-only file descriptor read/write?
MAP_PRIVATE ought to do it.
