From: Andrew Morton <akpm@osdl.org>
To: Hans Reiser <reiser@namesys.com>
Cc: 7atbggg02@sneakemail.com, linux-kernel@vger.kernel.org
Subject: Re: vm-pageout-throttling.patch: hanging in throttle_vm_writeout/blk_congestion_wait
Date: Tue, 16 Nov 2004 20:14:35 -0800 [thread overview]
Message-ID: <20041116201435.28554599.akpm@osdl.org> (raw)
In-Reply-To: <419A2698.4080900@namesys.com>
Hans Reiser <reiser@namesys.com> wrote:
>
> >>>loop-AES-2.2d)... I think (!) it caused this deadlock.
> >>>
> >>>
> >>That's not at all surprising. See the swap_extent work Andrew did
> >>for 2.5 (in mm/swapfile.c), by which swap to a swapfile now avoids
> >>the filesystem altogether (except while swapon prepares the map of
> >>disk blocks). By swapping to a loop device over a file, you're
> >>sneaking past his work, and putting the filesystem back under swap.
> >>
> >>
>
> Does Andrew's approach prevent putting swap on a compressed file (useful
> for reiser4 once the compression plugin is stable, not reiserfs)? (And
> no, I don't have any idea what the performance effect of that would be
> before it is tried and benchmarked....)
swapfiles bypass the filesystem completely, so if you're implementing
compression at the writepage() level, swap will cheerfully ignore all that
and will launch submit_bio() direct against your blockdev anyway.
encrypted swap should be done via dm-crypt. compressed swap would I guess
require dm-compress.
next prev parent reply other threads:[~2004-11-17 4:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 1:26 vm-pageout-throttling.patch: hanging in throttle_vm_writeout/blk_congestion_wait Sami Farin
2004-11-15 21:56 ` Hugh Dickins
2004-11-15 22:37 ` Sami Farin
2004-11-15 22:51 ` Ryan Cumming
2004-11-15 23:17 ` Sami Farin
2004-11-15 23:56 ` Andrew Morton
2004-11-16 16:11 ` Hans Reiser
2004-11-17 4:14 ` Andrew Morton [this message]
2004-11-17 11:38 ` Jari Ruusu
[not found] <fa.hmuv5gp.g5krg5@ifi.uio.no>
[not found] ` <fa.c8odfd2.1a3mtig@ifi.uio.no>
2004-11-17 23:07 ` Bodo Eggert
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=20041116201435.28554599.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=7atbggg02@sneakemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.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