From: Daniel Phillips <phillips@bonn-fries.net>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Memory Problem in 2.4.9 ?
Date: Wed, 22 Aug 2001 02:43:37 +0200 [thread overview]
Message-ID: <20010822003706Z16145-32383+770@humbolt.nl.linux.org> (raw)
In-Reply-To: <20010821154617.4671f85d.skraw@ithnet.com> <20010821190414Z16086-32384+294@humbolt.nl.linux.org> <20010822020445.435ec6d5.skraw@ithnet.com>
In-Reply-To: <20010822020445.435ec6d5.skraw@ithnet.com>
On August 22, 2001 02:04 am, Stephan von Krawczynski wrote:
> Daniel Phillips <phillips@bonn-fries.net> wrote:
>
> > > Aug 21 20:14:51 admin kernel: __alloc_pages: 3-order allocation failed
> > > (gfp=0x20/0).
> > > Aug 21 20:14:51 admin last message repeated 146 times
> > >
> > > Next idea?
> >
> > It's an atomic allocation, the driver is supposed to be able to handle
> > this, and it does since you report that the burn just runs slowly, it
> > does not stop. There is way too much in cache:
> >
> > > total: used: free: shared: buffers: cached:
> > > Mem: 1053675520 1047502848 6172672 0 20930560 939307008
> > > Swap: 271392768 15880192 255512576
> >
> > This is causing the high order allocation failures - with only a small
> > fraction of memory free the chances of none of it being in contiguous,
> > aligned 8 page units rises dramatically.
>
> I basically thought the same. In fact I do not understand why. Are there any
> parameters tunable to balance the whole picture a bit more towards the free
> pages?
I'd like to try to isolate the cause a little more. Can you please try the
following patch and see if it improves the cache balance. (This would not
be a good solution, it will just help show what is happening.)
--- ../2.4.9.clean/mm/filemap.c Thu Aug 16 14:12:07 2001
+++ ./mm/filemap.c Wed Aug 22 01:11:44 2001
@@ -980,7 +980,7 @@
static inline void check_used_once (struct page *page)
{
if (!PageActive(page)) {
- if (page->age)
+ if (page->age > 8)
activate_page(page);
else {
page->age = PAGE_AGE_START;
next prev parent reply other threads:[~2001-08-22 0:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010821174918Z16114-32383+718@humbolt.nl.linux.org>
2001-08-21 13:46 ` Stephan von Krawczynski
2001-08-21 14:33 ` Daniel Phillips
[not found] ` <20010821194140.43b46b10.skraw@ithnet.com>
2001-08-21 18:17 ` Stephan von Krawczynski
2001-08-21 19:10 ` Daniel Phillips
2001-08-22 0:04 ` Stephan von Krawczynski
2001-08-22 0:43 ` Daniel Phillips [this message]
2001-08-22 0:48 ` Rik van Riel
2001-08-22 1:13 ` Daniel Phillips
2001-08-22 11:01 ` Stephan von Krawczynski
2001-08-22 17:22 ` Mike Galbraith
2001-08-22 19:18 ` Stephan von Krawczynski
2001-08-23 4:57 ` Mike Galbraith
2001-08-22 10:43 ` Stephan von Krawczynski
2001-08-22 11:52 ` Stephan von Krawczynski
2001-08-22 4:47 Tommy Wu
2001-08-22 19:32 ` Daniel Phillips
2001-08-22 19:05 ` Marcelo Tosatti
2001-08-23 1:11 ` Daniel Phillips
2001-08-23 0:10 ` Marcelo Tosatti
2001-08-23 2:29 ` Daniel Phillips
2001-08-23 1:19 ` Marcelo Tosatti
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=20010822003706Z16145-32383+770@humbolt.nl.linux.org \
--to=phillips@bonn-fries.net \
--cc=linux-kernel@vger.kernel.org \
--cc=skraw@ithnet.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
all inboxes | Powered by JetHome®