linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jari Ruusu <jari.ruusu@pp.inet.fi>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Jens Axboe <axboe@suse.de>,
	Marcelo Tosatti <marcelo@conectiva.com.br>,
	Herbert Valerio Riedel <hvr@hvrlab.org>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.4.19pre3aa2
Date: Sat, 16 Mar 2002 14:10:27 +0200	[thread overview]
Message-ID: <3C933633.891663B0@pp.inet.fi> (raw)
In-Reply-To: <20020314032801.C1273@dualathlon.random> <3C912ACF.AF3EE6F0@pp.inet.fi> <20020315105621.GA22169@suse.de> <3C9230C6.4119CB4C@pp.inet.fi> <20020315185747.P10073@dualathlon.random>

Andrea Arcangeli wrote:
> Nevertheless as Jens said the infinite-loop-allocation in the
> ->make_request_fn path are deadlock prone at the moment, not because
> they sleeps but because they need a reserved mempool to guarantee
> operations can go ahead slowly without deadlocks even if dynamic
> allocation fails, but this is not a very pratical problem, it's very
> unlikely to deadlock there (it's not worse than the other infinite loop
> in getblk() that affects not just loop).

Unlikely to deadlock for normal filesystems, but swap on encrypted loop is a
different case.

Deadlock free operation is exactly why my prealloc loop patch is needed.
Beyond initial preallocating that is done at losetup time, it does not
allocate anything from kernel memory pools, but effectively recycles its
private per loop device preallocated memory. Encrypted swap needs that, and
normal device backed loop file systems are also happy with deadlock free and
VM stress free operation.

Regards,
Jari Ruusu <jari.ruusu@pp.inet.fi>

  reply	other threads:[~2002-03-16 12:11 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-14  2:28 2.4.19pre3aa2 Andrea Arcangeli
2002-03-14 12:32 ` 2.4.19pre3aa2 Dave Jones
2002-03-14 12:37   ` 2.4.19pre3aa2 Andrea Arcangeli
2002-03-14 12:46   ` 2.4.19pre3aa2 Jeff Garzik
2002-03-14 12:59     ` 2.4.19pre3aa2 Dave Jones
2002-03-14 15:53   ` 2.4.19pre3aa2 Bill Davidsen
2002-03-14 16:12     ` 2.4.19pre3aa2 Andrea Arcangeli
2002-03-14 16:16       ` 2.4.19pre3aa2 Dave Jones
2002-03-14 16:32         ` 2.4.19pre3aa2 Andrea Arcangeli
2002-03-16  1:26       ` 2.4.19pre3aa2 Mike Fedyk
2002-03-14 16:13     ` 2.4.19pre3aa2 Dave Jones
2002-03-14 17:16       ` 2.4.19pre3aa2 Bill Davidsen
2002-03-14 21:16   ` 2.4.19pre3aa2 H. Peter Anvin
2002-03-14 18:00 ` 2.4.19pre3aa2 Andrew Morton
2002-03-14 22:57 ` 2.4.19pre3aa2 Jari Ruusu
2002-03-15 10:56   ` 2.4.19pre3aa2 Jens Axboe
2002-03-15 11:06     ` 2.4.19pre3aa2 Jens Axboe
2002-03-15 17:35     ` 2.4.19pre3aa2 Jari Ruusu
2002-03-15 17:57       ` 2.4.19pre3aa2 Andrea Arcangeli
2002-03-16 12:10         ` Jari Ruusu [this message]
2002-03-16 13:54           ` 2.4.19pre3aa2 Andrea Arcangeli
2002-03-18 19:13       ` 2.4.19pre3aa2 Jens Axboe
2002-03-19 23:26         ` 2.4.19pre3aa2 Jari Ruusu
2002-03-20  7:54           ` 2.4.19pre3aa2 Jens Axboe
2002-03-20 18:16             ` 2.4.19pre3aa2 Jari Ruusu
2002-03-20 14:21           ` 2.4.19pre3aa2 Herbert Valerio Riedel
2002-03-15 12:19 ` 2.4.19pre3aa2 Herbert Valerio Riedel
2002-03-15 17:36   ` 2.4.19pre3aa2 Jari Ruusu
2002-03-15 18:36   ` 2.4.19pre3aa2 Herbert Valerio Riedel
2002-03-16 12:12     ` 2.4.19pre3aa2 Jari Ruusu

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=3C933633.891663B0@pp.inet.fi \
    --to=jari.ruusu@pp.inet.fi \
    --cc=andrea@suse.de \
    --cc=axboe@suse.de \
    --cc=hvr@hvrlab.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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;
as well as URLs for NNTP newsgroup(s).