From: Bill Davidsen <davidsen@tmr.com>
To: David Newall <davidn@davidnewall.com>
Cc: Vegard Nossum <vegard.nossum@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Swap on loop device on tmpfs locks up machine
Date: Sat, 27 Sep 2008 13:38:27 -0400 [thread overview]
Message-ID: <48DE6F93.9030002@tmr.com> (raw)
In-Reply-To: <48DE2BF7.3060905@davidnewall.com>
David Newall wrote:
> Vegard Nossum wrote:
>> It turns out that swap over loop device on tmpfs will lock up the
>> machine.
>
> Doesn't tmpfs use otherwise-free virtual memory? I expect the machine
> would lock up if you put swap (i.e. additional virtual memory) on such a
> device.
To reinstate the paragraph from the O.P. you snipped:
>> I'm not sure it's really a very good idea to do this in the first
>> place, but should something give a warning or prevent a user from
>> doing it?
I think you are both right, it is a bad thing to do, it does seem to lock up,
and something should prevent a user from doing that. But it may be easier to fix
the lockup than get the "prevent" right, there appears to be a loop there.
Just a simple questions to the O.P.: what were you thinking?!! Or was this a
test just to see what would happen?
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
next prev parent reply other threads:[~2008-09-27 17:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-26 18:46 Swap on loop device on tmpfs locks up machine Vegard Nossum
2008-09-27 12:49 ` David Newall
2008-09-27 17:38 ` Bill Davidsen [this message]
2008-09-27 18:30 ` Vegard Nossum
2008-09-28 15:18 ` Hugh Dickins
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=48DE6F93.9030002@tmr.com \
--to=davidsen@tmr.com \
--cc=davidn@davidnewall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vegard.nossum@gmail.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