From: Marcelo Tosatti <marcelo@conectiva.com.br>
To: David Whysong <dwhysong@physics.ucsb.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: __alloc_pages: 4-order allocation failed
Date: Thu, 5 Jul 2001 21:23:43 -0300 (BRT) [thread overview]
Message-ID: <Pine.LNX.4.21.0107052120460.1030-100000@freak.distro.conectiva> (raw)
In-Reply-To: <Pine.LNX.4.30.0107051730330.13297-100000@sal.physics.ucsb.edu>
On Thu, 5 Jul 2001, David Whysong wrote:
> Jes Sorensen (jes@sunsite.dk) wrote:
>
> >You ran out of memory, ie. there were no more free blocks of 16
> >consecutive pages available in the system. This is what happens on a
> >system with little memory or which is loaded with memory intensive
> >applications.
>
> I'm seeing the same thing here on a machine with 256 MB RAM and 1.5
> gigabytes of swap. There is no chance I am using anywhere near that
> much virtual memory.
>
> Something is wrong with the MM in 2.4.6-pre9.
David,
The messages are "harmless". The SCSI layer is trying to allocate big
chunks of memory (for the scattergather tables IIRC) just as an
optimization.
If its not possible to allocate big chunks, the SCSI code will use lower
order allocations. (smaller chunks)
next prev parent reply other threads:[~2001-07-06 1:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-06 0:33 __alloc_pages: 4-order allocation failed David Whysong
2001-07-06 0:23 ` Marcelo Tosatti [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-02 16:59 Ho Chak Hung
2001-07-05 21:25 ` Jes Sorensen
[not found] <Pine.LNX.4.10.10104252238590.3810-100000@coffee.psychology.mcmaster.ca>
2001-04-26 12:11 ` Feng Xian
2001-04-26 1:09 Feng Xian
2001-04-26 1:48 ` Marcelo Tosatti
2001-04-26 12:09 ` Feng Xian
2001-04-26 12:30 ` Andi Kleen
2001-04-26 13:50 ` Feng Xian
2001-04-26 13:53 ` Andi Kleen
2001-04-26 13:56 ` Feng Xian
2001-04-26 6:15 ` Jeff V. Merkey
2001-04-26 8:57 ` Mike Galbraith
2001-04-26 18:00 ` Szabolcs Szakacsits
2001-04-26 17:33 ` Jeff V. Merkey
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=Pine.LNX.4.21.0107052120460.1030-100000@freak.distro.conectiva \
--to=marcelo@conectiva.com.br \
--cc=dwhysong@physics.ucsb.edu \
--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;
as well as URLs for NNTP newsgroup(s).