From: Andrew Walrond <andrew@walrond.org>
To: linux-kernel@vger.kernel.org
Cc: "Guy" <bugzilla@watkins-home.com>,
"'Mike Hardy'" <mhardy@h3c.com>,
"'Jesper Juhl'" <juhl-lkml@dif.dk>,
linux-raid@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: No swap can be dangerous (was Re: swap on RAID (was Re: swp - Re: ext3 journal on software raid))
Date: Fri, 7 Jan 2005 09:28:13 +0000 [thread overview]
Message-ID: <200501070928.13307.andrew@walrond.org> (raw)
In-Reply-To: <200501062316.j06NFP900855@www.watkins-home.com>
On Thursday 06 January 2005 23:15, Guy wrote:
> If I MUST/SHOULD have swap space....
> Maybe I will create a RAM disk and use it for swap! :) :) :)
Well, indeed, I had the same thought. As long as you could guarantee that the
ram was of the highmem/non-dmaable type...
But we're getting ahead of ourselves. I think we need an authoritive answer to
the original premise. Perhaps Alan (cc-ed) might spare us a moment?
Did I dream this up, or is it correct?
"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."
Andrew
next prev parent reply other threads:[~2005-01-07 9:28 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 ` No swap can be dangerous (was Re: swap on RAID (was Re: swp - Re: ext3 journal on software raid)) Andrew Walrond
2005-01-06 22:34 ` Jesper Juhl
2005-01-06 22:57 ` Mike Hardy
2005-01-06 23:15 ` Guy
2005-01-07 9:28 ` Andrew Walrond [this message]
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=200501070928.13307.andrew@walrond.org \
--to=andrew@walrond.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bugzilla@watkins-home.com \
--cc=juhl-lkml@dif.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mhardy@h3c.com \
/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