From: David Brown <dave@spoonguard.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: "Page allocation failure" messages with sendfile() and cryptoloop
Date: Thu, 18 Mar 2004 01:09:50 -0500 [thread overview]
Message-ID: <20040318060950.GA2906@spoonguard.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 792 bytes --]
Hi:
I'm using Apache 2 to serve some rather large files from an XFS
volume on Linux 2.6.1. The XFS volume sits on a cryptoloop device,
which is in turn backed by a raw device (a partition on an IDE disk).
Apache 2 uses sendfile() to send static content. I'm seeing messages
like this when trying to send files whose size exceeds the available
RAM+swap:
httpd: page allocation failure. order:0, mode:0x1d2
Seemingly polynomial slowdowns are also apparent. I can send a 7MB file
instantly, and a 220MB file without too much delay. I gave up on the 600MB
file after 10 minutes of unresponsiveness.
The machine does stay alive through all of this.
Are there any issues with the cryptoloop driver and sendfile()? Should I
try 2.6.4, or would more information be helpful?
Thanks,
- Dave
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2004-03-18 6:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040318060950.GA2906@spoonguard.org \
--to=dave@spoonguard.org \
--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
all inboxes | Powered by JetHome®