public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Walrond <andrew@walrond.org>
To: linux-raid@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: No swap can be dangerous (was Re: swap on RAID (was Re: swp - Re: ext3 journal on software raid))
Date: Thu, 6 Jan 2005 22:08:39 +0000	[thread overview]
Message-ID: <200501062208.39563.andrew@walrond.org> (raw)
In-Reply-To: <41DD798F.8030902@h3c.com>

On Thursday 06 January 2005 17:46, Mike Hardy wrote:
>
> 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...

Andrew Walrond

       reply	other threads:[~2005-01-06 22:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <41DC9420.5030701@h3c.com>
     [not found] ` <20050106093811.GB99565@caffreys.strugglers.net>
     [not found]   ` <41DD798F.8030902@h3c.com>
2005-01-06 22:08     ` Andrew Walrond [this message]
2005-01-06 22:34       ` No swap can be dangerous (was Re: swap on RAID (was Re: swp - Re: ext3 journal on software raid)) Jesper Juhl
2005-01-06 22:57         ` Mike Hardy
2005-01-06 23:15           ` Guy
2005-01-07  9:28             ` Andrew Walrond
2005-02-28 20:07               ` Guy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200501062208.39563.andrew@walrond.org \
    --to=andrew@walrond.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox