Thread (85 messages) 85 messages, 22 authors, 2005-03-01

Re: No swap can be dangerous (was Re: swap on RAID (was Re: swp - Re: ext3 journal on software raid))

From: Mike Hardy <hidden>
Date: 2005-01-06 23:03:51
Also in: lkml


Jesper Juhl wrote:
On Thu, 6 Jan 2005, Andrew Walrond wrote:

quoted
On Thursday 06 January 2005 17:46, Mike Hardy wrote:
quoted
You are correct that I was getting at the zero swap argument - and I
agree that it is vastly different from simply not expecting it. It is
important to know that there is no inherent need for swap in the kernel
though - it is simply used as more "memory" (albeit slower, and with
some optimizations to work better with real memory) and if you don't
need it, you don't need it.
If I recollect a recent thread on LKML correctly, your 'no inherent need for 
swap' might be wrong.

I think the gist was this: the kernel can sometimes needs to move bits of 
memory in order to free up dma-able ram, or lowmem. If I recall correctly, 
the kernel can only do this move via swap, even if there is stacks of free 
(non-dmaable or highmem) memory.

I distinctly remember the moral of the thread being "Always mount some swap, 
if you can"

This might have changed though, or I might have got it completely wrong. - 
I've cc'ed LKML incase somebody more knowledgeable can comment...

http://kerneltrap.org/node/view/3202
Interesting - I was familiar with the original swappiness thread 
(http://kerneltrap.org/node/view/3000) but haven't seen anything since 
then (I mainly follow via kernel-traffic - enjoyable, but nowhere near 
real time). There's clearly been a bunch more discussion...

Not to rehash the performance arguments, but it appears from my read of 
the kernel trap page referenced above that the primary argument for swap 
is still the performance argument - I didn't see anything referencing 
swap being necessary to move DMAable ram or lowmem. Was that posted 
previously on linux-kernel but not on kerneltrap?

I'm still under the impression that "to swap or not" is a 
performance/policy/risk-management question, not a correctness question. 
If I'm wrong, I'd definitely like to know...

-Mike
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help