public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Kujau <evil@g-house.de>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, linux-crypto@nl.linux.org
Subject: Re: 2.4.24 + cryptoloop: __alloc_pages: 5-order allocation failed
Date: Thu, 19 Feb 2004 08:37:06 +0100	[thread overview]
Message-ID: <403467A2.6020402@g-house.de> (raw)
In-Reply-To: <Pine.LNX.4.58L.0402182037320.11790@logos.cnet>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Marcelo Tosatti wrote:
|
| Please do
|
| echo 1 > /proc/sys/vm/vm_gfp_debug
|

unfortunately i am not able to do this right now, i'll have access to
the machine on sunday i guess. so i have to wait what it gives then.

| I suspect the problem is loop allocates its buffers in a way so that the
| allocator can't sleep waiting for IO, which in turn overloads the memory
| and causes the failures.

yes, i've heard rumors too that the loop device was not so good at all
when it comes to high i/o throughput.

Thanks,
Christian.
- --
BOFH excuse #63:

not properly grounded, please bury computer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFANGeh+A7rjkF8z0wRApHdAKDHxhC2WdWbSQGROyY0vhIl0pdTUwCg0+aV
UESKUigO8UARal6xi+NzqHQ=
=nwc6
-----END PGP SIGNATURE-----

  reply	other threads:[~2004-02-19  7:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-17  2:08 2.4.24 + cryptoloop: __alloc_pages: 5-order allocation failed Christian Kujau
2004-02-18 23:42 ` Marcelo Tosatti
2004-02-19  7:37   ` Christian Kujau [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-25  4:04 Christian

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=403467A2.6020402@g-house.de \
    --to=evil@g-house.de \
    --cc=linux-crypto@nl.linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.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