public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jari Ruusu <jariruusu@users.sourceforge.net>
To: Sami Farin <7atbggg02@sneakemail.com>
Cc: linux-kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: vm-pageout-throttling.patch: hanging in  throttle_vm_writeout/blk_congestion_wait
Date: Wed, 17 Nov 2004 13:38:36 +0200	[thread overview]
Message-ID: <419B383C.CE11D38C@users.sourceforge.net> (raw)
In-Reply-To: 20041115223709.GD6654@m.safari.iki.fi

Sami Farin wrote:
> On Mon, Nov 15, 2004 at 09:56:29PM +0000, Hugh Dickins wrote:
> > On Mon, 15 Nov 2004, Sami Farin wrote:
> > >
> > > this time I had some swapspace on /dev/loop1 (file-backed, reiserfs,
> > > 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.
> 
> Aha...  interesting.
> 
> > It is begging for deadlocks: I'm not saying it couldn't be got to
> > work, and of course it would be nice to boast that there's no such
> > issue; but there are so many better places to invest such effort...
> 
> So, this was a known issue and it's hard to fix?  I didn't know that.
> 
> I know it's a "nicer" idea to use some partition for the swap
> instead of a file on reiserfs, but I created too small swap partitions
> originally and I can't(/bother?) resize the other partitions.
> And sometimes some memhog forces me to add even more swap.

Quote from loop-AES' README file:
"
7.1. Example 1 - Encrypting swap on 2.4 and newer kernels
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Device backed (partition backed) loop is capable of encrypting swap on 2.4
and newer kernels. File backed loops can't be used for swap.
"

That "file backed loops can't be used for swap" warning has been there in
that README file since September 2001.

-- 
Jari Ruusu  1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9  DB 1D EB E3 24 0E A9 DD

  parent reply	other threads:[~2004-11-17 11:36 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
2004-11-17 11:38     ` Jari Ruusu [this message]
     [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=419B383C.CE11D38C@users.sourceforge.net \
    --to=jariruusu@users.sourceforge.net \
    --cc=7atbggg02@sneakemail.com \
    --cc=linux-kernel@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