From: Roger Larsson <roger.larsson@skelleftea.mail.telia.com>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][RFC] simpler __alloc_pages{_limit}
Date: Sat, 25 Aug 2001 21:24:40 +0200 [thread overview]
Message-ID: <200108251929.f7PJT5Q06766@mailf.telia.com> (raw)
In-Reply-To: <200108242253.f7OMrbQ20401@mailf.telia.com> <200108250055.f7P0tGh28170@mailg.telia.com> <20010825135508.5afe1988.skraw@ithnet.com>
In-Reply-To: <20010825135508.5afe1988.skraw@ithnet.com>
On Saturdayen den 25 August 2001 13:55, Stephan von Krawczynski wrote:
> On Sat, 25 Aug 2001 02:48:28 +0200
>
> 2) It does not really work around the basic problem of too
> many cached pages in case of heavy filesystem action, I do get the already
> known "kernel: __alloc_pages: 2-order allocation failed." by simply copying
> files a lot.
Hi again,
I would like to see from were these higher order allocs comes from.
Please insert something like this:
printk("pid=%d; __alloc_pages(gfp=0x%x, order=%ld, ...)\n",
current->pid, gfp_mask, order);
show_trace(NULL);
(You have something resembling the first line - I added this in the beginning
of __alloc_pages, you may add it together with the error message)
If everything is ok (correct Symbols.map) you should be able to get
a symbolic call trace in /var/logs/messages
(some are false positives, but they can be filtered out manually)
/RogerL
--
Roger Larsson
Skellefteå
Sweden
next prev parent reply other threads:[~2001-08-25 19:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200108242253.f7OMrbQ20401@mailf.telia.com>
2001-08-25 0:48 ` Roger Larsson
2001-08-25 8:48 ` Mike Galbraith
2001-08-25 18:09 ` Daniel Phillips
2001-08-25 19:53 ` Mike Galbraith
2001-08-25 11:55 ` Stephan von Krawczynski
2001-08-25 16:25 ` Roger Larsson
2001-08-25 19:24 ` Roger Larsson [this message]
2001-08-28 11:22 ` Stephan von Krawczynski
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=200108251929.f7PJT5Q06766@mailf.telia.com \
--to=roger.larsson@skelleftea.mail.telia.com \
--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®