View Single Post
Posts: 330 | Thanked: 556 times | Joined on Oct 2012
#270
Originally Posted by sixwheeledbeast View Post
free is not equal to flopswap's values.
You see flopswap is measuring the fresh (clean) swap that has been written not the amount in use.

To make this clear in an example, when flopswap hits 100% it doesn't mean you have no swap left, it means you have no "fresh" swap left and you may now see the slowing effect of swap fragmentation.
Thank you for your explanations, sixwheeledbeast.

Everything makes sense and is clear, except the objection misiak proposed (I actually thought about this before I even saw his response ).

It seems (at first sight, anyway) that the percentage of fresh swap remaining should be <= the total amount of swap space remaining reported by free.

But I'm sure I'm wrong and you will clarify things.

EDIT: One way I see this being possible is if the way FlopSwap works is by partitioning the swap space. So you might keep internally a cursor where you start writing sequentially (which is set for example when you make a fresh swap), but which is different of how free swap space is calculated by the free command.

Just speculating.

Last edited by malfunctioning; 2014-10-20 at 18:47.
 

The Following User Says Thank You to malfunctioning For This Useful Post: