From: Pavel Machek <pavel@ucw.cz>
To: John Richard Moser <nigelenki@comcast.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Swap on Fuse deadlocks?
Date: Tue, 26 Sep 2006 00:04:26 +0200 [thread overview]
Message-ID: <20060925220426.GA2546@elf.ucw.cz> (raw)
In-Reply-To: <45184D88.1010203@comcast.net>
On Mon 2006-09-25 17:43:36, John Richard Moser wrote:
> I just tried to set up an LZOlayer swap partition:
>
> http://north.one.pl/~kazik/pub/LZOlayer/
>
> The layout was as such:
>
> /tmp/swap_base - tmpfs (run1), disk (run2)
> /tmp/swap - lzolayer swap_base
> /tmp/swap/swap0 - 200M swap file
> /dev/loop0 - /tmp/swap/swap0 loopback
>
> I turned on loop0, crept anywhere over 10 megs into swap and it seized
> up (otherwise it was fine). This happened in both run1 (swap on tmpfs)
> and run2 (swap on disk).
>
> The swap on tmpfs I can understand; it'll essentially loop trying to
> allocate new swap, swap in and out parts of the swap file to itself, and
> eventually hit a condition where it's trying to swap an area of the swap
> file into itself, creating an infinite loop.
>
> Swap on disk I don't get. A little slow perhaps due to the LZO or zlib
> compression in the middle (lzolayer lets you pick either); but a total
> freeze? What's wrong here, is lzo_fs data getting swapped out and then
> not swapped in because it's needed to decompress itself?
Yes, possibly. Or maybe lzo_fs needs to allocate memory and kernel
decides it needs to swap for that?
It is miracle that fuse works for normal write, do not expect it to
work for swap. (Does it even work mmap-ed writes?)
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2006-09-25 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-25 21:43 Swap on Fuse deadlocks? John Richard Moser
2006-09-25 22:04 ` Pavel Machek [this message]
2006-09-26 17:54 ` Miklos Szeredi
2006-09-26 0:08 ` David Schwartz
2006-09-26 12:13 ` Pavel Machek
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=20060925220426.GA2546@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=nigelenki@comcast.net \
/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