Today we emit a swap warning when swappiness is set outside of 0 or 1 on Linux to help users configure MongoDB as per our recommentations. However users commonly disable swap when there is sufficient memory on the host system which leads to a confusing error message when swappiness is set to something other than 0 or 1 as the swappiness setting has no impact on systems where swap isn't enabled (as far as I know).

We should avoid emitting this warning when the system has swap disabled if possible in order to avoid alarming users.