Sure ??? Where ?? What disk space uses it to swap pages to ?
>(This is why you can still get "disk thrashing" without any swap - in fact,
>it's more likely in this case than it is with some swap added - you are just
>forcing your binaries to take more of the swapping load instead.)
>
You get thrashing because you don have anything cached. So you can get a point
(fill all your space with apps and data) where each file read is _REALLY_ a
disk read, not just a transfer from cache (that is what usually happens).
>
>So: with swapspace, the kernel swaps out a few hundred Mb of unused data, to
>make room for more code. Without it, the kernel is forced to swap out code
>pages instead. The big news here is...?
>
You swap out pages, not data or code. Kernel does not care if the page contains
code or data. Try (on a swap enabled box) this: open mozilla or staroffice (a
big gui app), let it open and don't use it, fill your ram with other apps and
try to pull down a menu from mozilla. It has an unusual delay, the time to get
mozilla CODE pages back from swap. That is why a system with no swap is more
responsive.
Yes, a box without swap runs faster, but if you *don't do anything* with it. The test
shown in previous mails had a ton of apps opened *doing nothing*. Try do do
a grep several times on the kernel source tree for example in that scenario.
Or a kernel build. They will be dog slow (all the tries). Try the same on
a box with swap, the second time much things are cached and it flies.
-- J.A. Magallon # Let the source be with you... mailto:jamagallon@able.es Mandrake Linux release 8.2 (Cooker) for i586 Linux werewolf 2.4.15-pre6-beo #1 SMP Sun Nov 18 10:25:01 CET 2001 i686 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/