3 ms·
The 'right' answer is to stop allocating swap in a separate partition, and share swap space with the filesystem. Whether you do this with an LVM, or by pinning
by 95014_refugee 8y ago
The 'right' answer is to stop allocating swap in a separate partition, and share swap space with the filesystem.
Whether you do this with an LVM, or by pinning files and swapping to their underlying extents is less important. But assuming at system setup time that you can bound the amount of swap that will be required in the future to support some specific workload is silly, and in order to avoid being wrong, you have to penalise most systems most of the time.
- genpfault 8y ago> The 'right' answer is to stop allocating swap in a separate partition, and share swap space with the filesystem. Does hibernate/suspend-to-disk work with non-partition swap? IIRC that is/was a limitation.
- colanderman 8y agoIt does, but your suspend-to-disk tool has to support it. (Linux supports discontiguous swap – and therefore suspend-to-disk – in general. The suspend-to-disk mechanism just needs to know where the suspend space starts, and the mechanism of determining that varies by filesystem.) See https://www.kernel.org/doc/Documentation/power/swsusp.txt https://www.kernel.org/doc/Documentation/power/swsusp.txt