From: Andrea Arcangeli <andrea@suse.de>
To: Lukas Hejtmanek <xhejtman@mail.muni.cz>
Cc: "J.A. Magallon" <jamagallon@able.es>,
Austin Gonyou <austin@digitalroadkill.net>,
linux-kernel@vger.kernel.org, linux-scsi@dualathlon.random
Subject: Re: Terrible VM in 2.4.11+ again?
Date: Wed, 10 Jul 2002 18:34:22 +0200 [thread overview]
Message-ID: <20020710163422.GB2513@dualathlon.random> (raw)
In-Reply-To: <20020709124807.D1510@mail.muni.cz>
On Tue, Jul 09, 2002 at 12:48:08PM +0200, Lukas Hejtmanek wrote:
> On Tue, Jul 09, 2002 at 12:58:16AM +0200, J.A. Magallon wrote:
> > Seriously, if you have that kind of problems, take the -aa kernel and use it.
> > I use it regularly and it behaves as one would expect, and fast.
> > And please, report your results...
>
> I've tried 2.4.19rc1aa2, it swaps even when I have 512MB ram and xcdroast with
> scsi-ide emulation cd writer reports to syslog:
> Jul 9 12:45:02 hell kernel: __alloc_pages: 3-order allocation failed
> (gfp=0x20/0)
> Jul 9 12:45:02 hell kernel: __alloc_pages: 3-order allocation failed
> (gfp=0x20/0)
> Jul 9 12:45:02 hell kernel: __alloc_pages: 2-order allocation failed
> (gfp=0x20/0)
> Jul 9 12:45:02 hell kernel: __alloc_pages: 1-order allocation failed
> (gfp=0x20/0)
> Jul 9 12:45:02 hell kernel: __alloc_pages: 0-order allocation failed
> (gfp=0x20/0)
>
> Am I something missing?
you may want to reproduce with vm_debug set to 1, but I'm pretty sure
it's a scsi generic issue, they are allocating ram with GFP_ATOMIC, and
they may eventually fail if kswapd cannot keep up with the other
GFP_ATOMIC allocations. They should use GFP_NOIO, with -aa it won't even
try to unmap pages. It will just try to shrink clean cache and it
should work fine for the above purpose where the allocation needs low
latency (the local_pages per-task ensures their work won't be stolen by
the GFP_ATOMIC users). I asked for that change some time ago but it
never happened apparently. However I assume the sr layer tried some more
after failing, sg has a quite large queue so some delay isn't fatal, and
you can probably safely ignore the above messages, they're just warnings
for you. nevertheless GFP_NOIO would make the allocations more reliable.
Andrea
next prev parent reply other threads:[~2002-07-10 16:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-08 22:11 Terrible VM in 2.4.11+? Lukas Hejtmanek
2002-07-08 22:37 ` Austin Gonyou
2002-07-08 22:50 ` Lukas Hejtmanek
2002-07-08 22:58 ` J.A. Magallon
2002-07-08 23:58 ` Lukas Hejtmanek
2002-07-09 10:48 ` Terrible VM in 2.4.11+ again? Lukas Hejtmanek
2002-07-10 16:34 ` Andrea Arcangeli [this message]
[not found] ` <20020801113124.GA755@mail.muni.cz>
[not found] ` <20020801140348.GM1132@dualathlon.random>
[not found] ` <20020801141940.GB755@mail.muni.cz>
2002-08-01 15:39 ` Terrible VM in 2.4.19rc3aa4 once again? Andrea Arcangeli
[not found] ` <20020801220143.GC755@mail.muni.cz>
2002-08-01 22:14 ` Andrea Arcangeli
2002-07-10 8:43 ` Terrible VM in 2.4.11+? Thomas Tonino
2002-07-10 8:49 ` Jens Axboe
2002-07-10 13:52 ` Thomas Tonino
2002-07-10 16:41 ` Andrea Arcangeli
2002-07-10 12:34 ` Adrian Bunk
2002-07-08 23:04 ` Austin Gonyou
2002-07-08 23:27 ` khromy
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=20020710163422.GB2513@dualathlon.random \
--to=andrea@suse.de \
--cc=austin@digitalroadkill.net \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@dualathlon.random \
--cc=xhejtman@mail.muni.cz \
/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